From: Wang Jianchao <jianchao.wan9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Memcached with cfs quota 400% performance boost after bind to 4 cpus
Date: Fri, 17 Sep 2021 20:35:36 +0800 [thread overview]
Message-ID: <9f907d99-1cdb-37db-49ae-8e31c7ea8fe7@gmail.com> (raw)
Hi list
I have a test environment with following,
A memcached (memcached -d -m 50000 -u root -p 12301 -c 1000000 -t 16) in cpu cgroup with following config,
cpu.cfs_quota_us = 400000
cpu.cfs_period_us = 100000
And a mutilate loop (mutilate -s x.x.x.x:12301 -T 40 -c 20 -t 60 -W 5 -q 1000000) running on another host
w/o any cgroup config,
When bind memcached to 0-15 with cpuset,
==========================================
mutilate showed,
#type avg std min 5th 10th 90th 95th 99th
read 1275.8 6358.9 49.8 378.2 418.5 767.2 841.4 53998.5
update 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
op_q 1.0 0.0 1.0 1.0 1.0 1.1 1.1 1.1
Total QPS = 626566.2 (37594133 / 60.0s)
Misses = 0 (0.0%)
Skipped TXs = 0 (0.0%)
RX 9288150851 bytes : 147.6 MB/s
TX 1353390552 bytes : 21.5 MB/s
And perf on memcached showed,
635,602,955,852 cycles (30.07%)
479,554,401,177 instructions # 0.75 insn per cycle (40.02%)
12,585,059,799 L1-dcache-load-misses # 9.31% of all L1-dcache hits (50.07%)
135,140,424,785 L1-dcache-loads (49.96%)
76,849,156,759 L1-dcache-stores (50.02%)
45,700,267,543 L1-icache-load-misses (49.97%)
495,149,862 LLC-load-misses # 24.96% of all LL-cache hits (39.95%)
1,984,134,589 LLC-loads (39.97%)
327,130,920 LLC-store-misses (20.06%)
1,397,111,117 LLC-stores (20.06%)
When bind memcached to 0-3 with cpuset,
========================================
mutilate showed,
#type avg std min 5th 10th 90th 95th 99th
read 934.7 3669.3 41.1 112.8 129.5 385.3 3321.9 21923.7
update 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
op_q 1.0 0.0 1.0 1.0 1.0 1.1 1.1 1.1
Total QPS = 852885.6 (51173140 / 60.0s)
Misses = 0 (0.0%)
Skipped TXs = 0 (0.0%)
RX 12642165580 bytes : 200.9 MB/s
TX 1842259932 bytes : 29.3 MB/s
And perf on memcached showed,
621,311,916,151 cycles (30.01%)
599,835,965,997 instructions # 0.97 insn per cycle (40.02%)
12,585,889,988 L1-dcache-load-misses # 7.59% of all L1-dcache hits (50.00%)
165,750,518,361 L1-dcache-loads (50.01%)
93,588,611,989 L1-dcache-stores (50.00%)
44,445,213,037 L1-icache-load-misses (50.01%)
568,410,466 LLC-load-misses # 26.91% of all LL-cache hits (40.03%)
2,112,218,392 LLC-loads (40.00%)
261,202,604 LLC-store-misses (19.97%)
1,484,886,714 LLC-stores
We can see the IPC raised from 0.75 to 0.97, this should be the reason of the performance boost.
What does cause the IPC boost ?
Thanks a million for any help
Jianchao
next reply other threads:[~2021-09-17 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 12:35 Wang Jianchao [this message]
2021-09-17 13:01 ` Memcached with cfs quota 400% performance boost after bind to 4 cpus Peter Zijlstra
[not found] ` <9f907d99-1cdb-37db-49ae-8e31c7ea8fe7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-09-18 1:19 ` Wang Jianchao
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=9f907d99-1cdb-37db-49ae-8e31c7ea8fe7@gmail.com \
--to=jianchao.wan9-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox