From: "Edwin Török" <edwin.torok@cloud.com>
To: xen-devel@lists.xenproject.org
Cc: "Edwin Török" <edwin.torok@cloud.com>,
"Christian Lindig" <christian.lindig@citrix.com>,
"David Scott" <dave@recoil.org>, "Wei Liu" <wl@xen.org>,
"Anthony PERARD" <anthony.perard@citrix.com>
Subject: [PATCH v1 0/2] reduce oxenstored quota processing overhead under load
Date: Wed, 31 Jan 2024 10:52:54 +0000 [thread overview]
Message-ID: <cover.1706697858.git.edwin.torok@cloud.com> (raw)
A recent stress test with 1000 VMs has shown that oxenstored spends ~40% of time in Quota.copy,
even when processing read-only xenstore commands.
Use an immutable data structure instead.
I have tested this in the gitlab CI here: https://gitlab.com/xen-project/people/edwintorok/xen/-/pipelines/1158302827
For convenience the changes in this (and the other series I sent out) are also available as a git repository:
https://gitlab.com/xen-project/people/edwintorok/xen/-/compare/private%2Fedvint%2Fdune1x...private%2Fedvint%2Fno-hashtbl-dev?from_project_id=47263871&straight=false
I haven't yet measured the speedup, but thought to send out the patch for review early.
Edwin Török (2):
oxenstored: use Map instead of Hashtbl for quotas
oxenstored: make Quota.t pure
tools/ocaml/xenstored/quota.ml | 65 ++++++++++++++++++----------------
tools/ocaml/xenstored/store.ml | 17 +++++----
2 files changed, 44 insertions(+), 38 deletions(-)
--
2.43.0
next reply other threads:[~2024-01-31 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 10:52 Edwin Török [this message]
2024-01-31 10:52 ` [PATCH v1 1/2] oxenstored: use Map instead of Hashtbl for quotas Edwin Török
2024-01-31 10:52 ` [PATCH v1 2/2] oxenstored: make Quota.t pure Edwin Török
2024-01-31 11:17 ` Christian Lindig
2024-01-31 16:27 ` Edwin Torok
2024-02-23 11:35 ` Edwin Torok
2024-02-23 12:06 ` Andrew Cooper
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=cover.1706697858.git.edwin.torok@cloud.com \
--to=edwin.torok@cloud.com \
--cc=anthony.perard@citrix.com \
--cc=christian.lindig@citrix.com \
--cc=dave@recoil.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.