On 02/10/2015 01:13 PM, Stefan Priebe wrote:
Am 10.02.2015 um 20:10 schrieb Mark Nelson:
On 02/10/2015 12:55 PM, Stefan Priebe wrote:
Hello,
last year in june i already reported this but there was no real result.
(http://lists.ceph.com/pipermail/ceph-users-ceph.com/2014-July/041070.html)
I then had the hope that this will be fixed itself when hammer is
released. Now i tried hammer an the results are bad as before.
Since firefly librbd1 / librados2 are 20% slower for 4k random iop/s
than dumpling - this is also the reason why i still stick to dumpling.
I've now modified my test again to be a bit more clear.
Ceph cluster itself completely dumpling.
librbd1 / librados from dumpling (fio inside qemu): 23k iop/s for random
4k writes
- stopped qemu
- cp -ra firefly_0.80.8/usr/lib/librados.so.2.0.0 /usr/lib/
- cp -ra firefly_0.80.8/usr/lib/librbd.so.1.0.0 /usr/lib/
- start qemu
same fio, same qemu, same vm, same host, same ceph dumpling storage,
different librados / librbd: 16k iop/s for random 4k writes
What's wrong with librbd / librados2 since firefly?
Hi Stephen,
Just off the top of my head, some questions to investigate:
What happens to single op latencies?
How to test this?
try your random 4k write test using libaio, direct IO, and iodepth=1.
Actually it would be interesting to know how it is with higher IO depths
as well (I assume this is what you are doing now?) Basically I want to
know if single-op latency changes and whether or not it gets hidden or
exaggerated with lots of concurrent IO.
Does enabling/disabling RBD cache have any effect?
I've it enabled on both through qemu write back setting.
It'd be great if you could do the above test both with WB RBD cache and
with it turned off.
How's CPU usage? (Does perf report show anything useful?)
Can you get trace data?
I'm not familiar with trace or perf - what should do exactly?
you may need extra packages. Basically on VM host, during the test with
each library you'd do:
sudo perf record -a -g dwarf -F 99
(ctrl+c after a while)
sudo perf report --stdio > foo.txt
if you are on a kernel that doesn't have libunwind support:
sudo perf record -a -g
(ctrl+c after a while)
sudo perf report --stdio > foo.txt
Then look and see what's different. This may not catch anything though.
You should also try Greg's suggestion looking at the performance
counters to see if any interesting differences show up between the runs.
Stefan
Mark
Greets,
Stefan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
