[Bug 1894453] Re: Building Ceph packages with RelWithDebInfo

[Ponnuvel Palaniyappan]

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
[1] https://github.com/facebook/rocksdb/wiki/Read-Modify-Write-Benchmarks
[2] https://github.com/facebook/rocksdb/wiki/RocksDB-In-Memory-Workload-Performance-Benchmarks


** Attachment added: "rocksdb benchmarks.txt"
   https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1894453/+attachment/5415020/+files/rocksdb%20benchmarks.txt

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1894453

Title:
  Building Ceph packages with RelWithDebInfo

Status in ceph package in Ubuntu:
  In Progress

Bug description:
  This is to consider/discuss the possibility of whether the Ceph
  packages (UCA) should be built with RelWithDebInfo build option
  (CMAKE_BUILD_TYPE [0]) which can be supplied to the build script
  do_cmake.sh [1].

  Currently, Upstream as well as UCA builds default to 'Debug' [0]
  builds. But is any reason why shouldn't go for RelWithDebInfo (i.e.
  "Release with Debug information")?

  
  There's one issue noted with RelWithDebInfo which has a workaround too [2].

  In general, gcc's -O2 [3] build should generate better code as well as
  there's a specific case for Ceph [4] that it improves performance.

  [0] https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html

  [1] https://github.com/ceph/ceph/blob/master/do_cmake.sh

  [2] https://docs.ceph.com/docs/master/dev/perf/#common-issues

  [3] https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html

  [4] https://bugs.gentoo.org/show_bug.cgi?id=733316

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1894453/+subscriptions