Couchbase Server 2.0的数据压缩详解

jieforest

Compaction performance in Couchbase Server depends on IO capacity and proper cluster sizing. Your cluster must be properly sized so that there is enough capacity in all the various areas to support everything else the system is doing to maintain the required level of performance. So, how do you tune compaction in Couchbase Server?

There is no magic bullet here ... Depending on your application’s IOPS requirement, you need to size your cluster properly and might want to test your workload across a variety of different storage hardware.

If your app is write heavy, SSD’s might be the best option but for heavy read ratios, EBS might be a good solution at a low cost.

By default, if both data and view indexes are configured for auto-compaction, compaction operates sequentially, first on the database and then on the views.  By enabling parallel compaction, both the databases and views can be compacted at the same time.

This requires more CPU and disk I/O, but if the database and view indexes are stored on different physical disk devices (as is our best practice anyway), the two can complete in parallel so that the index and data files does not grow extremely large.

jieforest

Conclusion

At the end of the day, every database needs regular maintenance. Online compaction is a huge plus but you have to test your system and configure your compaction settings appropriately so that it does not affect your system load.

jieforest

over.