From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: [pve-devel] ceph : build option to double 4k write performance
Date: Wed, 3 Jan 2024 16:39:45 +0000 [thread overview]
Message-ID: <f2ddee700ea2fceed4531630229a8e6a4602b7f8.camel@groupe-cyllene.com> (raw)
Hi, (Happy New Year!)
I just found this ceph merge request
https://github.com/ceph/ceph/pull/54891
debian/rules: Fix build_type for massive performance gain
debian/rules
Viewed
@@ -29,6 +29,7 @@ extraopts += -DWITH_PYTHON3=3
extraopts += -DWITH_CEPHFS_JAVA=ON
extraopts += -DWITH_CEPHFS_SHELL=ON
extraopts += -DWITH_SYSTEMD=ON -DCEPH_SYSTEMD_ENV_DIR=/etc/default
extraopts += -DCMAKE_BUILD_TYPE=RelWithDebInfo
"After retesting with CMAKE_BUILD_TYPE properly set to RelWithDebInfo,
4K random write performance on the cluster doubled and RocksDB
compaction times were reduced by roughly 2-3X."
I think it could be great to apply it to proxmox ceph package, as 4k
write are really the slowest thing in ceph.
reply other threads:[~2024-01-03 16:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2ddee700ea2fceed4531630229a8e6a4602b7f8.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox