(Ignore my comments as I've managed to setup a cluster without needing ceph-deploy).
I have installed the packages and setup a cluster. The cluster was functional and found no issues with the Groovy packages in my tests.
I have done some of the Ceph's benchmarks [0] using the Ceph cluster. Also did some separate tests on rocksdb with and without those flags. Overall, the Ceph Cluster tests which were mainly focusing on I/O didn't show anything out of the ordinary. But the rocksdb benchmarks [1] [2] showed that the optimized build works better in most cases.
Besides, we already that this has already been enabled in Ceph upstream as you know -- which we'll get in the future releases. So I am positive that there are no cause for concern with these packages that you've built for Groovy.
Hi @Corey,
(Ignore my comments as I've managed to setup a cluster without needing ceph-deploy).
I have installed the packages and setup a cluster. The cluster was functional and found no issues with the Groovy packages in my tests.
I have done some of the Ceph's benchmarks [0] using the Ceph cluster. Also did some separate tests on rocksdb with and without those flags. Overall, the Ceph Cluster tests which were mainly focusing on I/O didn't show anything out of the ordinary. But the rocksdb benchmarks [1] [2] showed that the optimized build works better in most cases.
Besides, we already that this has already been enabled in Ceph upstream as you know -- which we'll get in the future releases. So I am positive that there are no cause for concern with these packages that you've built for Groovy.
[0] https:/ /tracker. ceph.com/ projects/ ceph/wiki/ Benchmark_ Ceph_Cluster_ Performance /github. com/facebook/ rocksdb/ wiki/Read- Modify- Write-Benchmark s /github. com/facebook/ rocksdb/ wiki/RocksDB- In-Memory- Workload- Performance- Benchmarks
[1] https:/
[2] https:/