What is the difference between bucket compact and compression mode?
If Compression mode is Active, is there no need to do Compact?
Not exactly, they’re actually quite separate things.
-
Compression refers to applying an algorithm to the data stored within Couchbase to reduce its size (i.e. snappy compression). There are a few different option here because it’s possible that the client may send the data compressed already, or may send it uncompressed and you want the server to compress it. There are very rare cases where the added CPU overhead of compression has a negative effect, so we allow for disabling it…but it’s very uncommon. You can read more about compression here: Compression | Couchbase Docs
-
Compaction can be best thought of as “garbage collection” for the on-disk files where the data is stored. Couchbase uses an append-only disk format which basically means every time data changes, a new copy is written to the end of the file instead of updating it in-place (lots of benefit for this - performance, anti-corruption, etc). The only drawback is that you end up with some disk space being taken up for data that is no longer used. Compaction is the process of periodically rewriting those files and deleting the previous copy to reclaim space: Storage Settings | Couchbase Docs
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.