From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH ceph 0/2] Build rocksdb in non-debug mode
Date: Tue, 9 Jan 2024 15:50:28 +0100 [thread overview]
Message-ID: <20240109145030.1647121-1-aderumier@odiso.com> (raw)
They are a bug in current debian packaging,
where rocksdb is build in debug mode (not inheriting from cmake flags)
patch 1 already exist in ubuntu
patch 2 is a newer patch commited in ceph recently
(patch 2 should be enough, but I'm keeping patch1 by security).
I have tested it, 4k randwrite iops x2,
fio: 4k randwrite:queue depth=64:sync write: cache=none:
before: 16000 iops
https://pbs.twimg.com/media/GDKu9dqXYAAeH4I?format=jpg&name=large
after: 38000 iops
https://pbs.twimg.com/media/GDKu9dqW8AA3dE8?format=jpg&name=large
sandre-win.altima-hosting.fr
sandre-win.altima-hosting.fr
and submit latency /3
https://pbs.twimg.com/media/GDFmBJOW8AApWYZ?format=jpg&name=large
Alexandre Derumier (2):
patch: debian/rules: fix build type
patch: add 0022-rocksb-inherit-parent-cmake-cxx-flags.patch
patches/0021-debian-rules-fix-buildtype.patch | 22 +++++++
...ocksb-inherit-parent-cmake-cxx-flags.patch | 57 +++++++++++++++++++
patches/series | 2 +
3 files changed, 81 insertions(+)
create mode 100644 patches/0021-debian-rules-fix-buildtype.patch
create mode 100644 patches/0022-rocksb-inherit-parent-cmake-cxx-flags.patch
--
2.39.2
next reply other threads:[~2024-01-09 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 14:50 Alexandre Derumier [this message]
2024-01-09 14:50 ` [pve-devel] [PATCH ceph 1/2] patch: debian/rules: fix build type Alexandre Derumier
2024-01-10 9:18 ` Fabian Grünbichler
2024-01-09 14:50 ` [pve-devel] [PATCH ceph 2/2] patch: add 0022-rocksb-inherit-parent-cmake-cxx-flags.patch Alexandre Derumier
2024-01-09 15:39 ` [pve-devel] [PATCH ceph 0/2] Build rocksdb in non-debug mode Thomas Lamprecht
2024-01-09 15:46 ` DERUMIER, Alexandre
2024-01-09 16:12 ` Thomas Lamprecht
2024-01-09 16:16 ` DERUMIER, Alexandre
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=20240109145030.1647121-1-aderumier@odiso.com \
--to=aderumier@odiso.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