[Bug 1894453] Re: Building Ceph packages with RelWithDebInfo

[Corey Bryant]

** Description changed:

- 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].
+ [Impact]
+ 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].
+ 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
+ 
+ [Test Case]
+ Standard ceph-backed OpenStack regression will be run, consisting of juju-deployed OpenStack+ceph and tempest regression testing against the deployment.
+ 
+ [Regression Potential]
+ As Ponnuvel mentioned, the size of binaries will be slightly bigger and also the build/compilation will be longer.

** Description changed:

  [Impact]
  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
  
  [Test Case]
  Standard ceph-backed OpenStack regression will be run, consisting of juju-deployed OpenStack+ceph and tempest regression testing against the deployment.
  
  [Regression Potential]
  As Ponnuvel mentioned, the size of binaries will be slightly bigger and also the build/compilation will be longer.
+ Ponnuvel also did a search of pponnuvel i'd search of upstream bugs at https://tracker.ceph.com and didn't find any relevant bugs.

-- 
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:
  Fix Released

Bug description:
  [Impact]
  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

  [Test Case]
  Standard ceph-backed OpenStack regression will be run, consisting of juju-deployed OpenStack+ceph and tempest regression testing against the deployment.

  [Regression Potential]
  As Ponnuvel mentioned, the size of binaries will be slightly bigger and also the build/compilation will be longer.
  Ponnuvel also did a search of pponnuvel i'd search of upstream bugs at https://tracker.ceph.com and didn't find any relevant bugs.

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