From: Jason Dillaman <dillaman@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1701449] Re: high memory usage when using rbd with client caching
Date: Mon, 01 Oct 2018 19:44:37 -0000 [thread overview]
Message-ID: <153842307795.2557.15891416982810791845.malone@wampee.canonical.com> (raw)
In-Reply-To: 149880297386.6544.11962739093038956076.malonedeb@gac.canonical.com
@Nick: if you can recreate the librbd memory growth, any chance you can
help test a potential fix [1]?
[1] https://github.com/ceph/ceph/pull/24297
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1701449
Title:
high memory usage when using rbd with client caching
Status in QEMU:
New
Bug description:
Hi,
we are experiencing a quite high memory usage of a single qemu (used with KVM) process when using RBD with client caching as a disk backend. We are testing with 3GB memory qemu virtual machines and 128MB RBD client cache. When running 'fio' in the virtual machine you can see that after some time the machine uses a lot more memory (RSS) on the hypervisor than she should. We have seen values (in real production machines, no artificially fio tests) of 250% memory overhead. I reproduced this with qemu version 2.9 as well.
Here the contents of our ceph.conf on the hypervisor:
"""
[client]
rbd cache writethrough until flush = False
rbd cache max dirty = 100663296
rbd cache size = 134217728
rbd cache target dirty = 50331648
"""
How to reproduce:
* create a virtual machine with a RBD backed disk (100GB or so)
* install a linux distribution on it (we are using Ubuntu)
* install fio (apt-get install fio)
* run fio multiple times with (e.g.) the following test file:
"""
# This job file tries to mimic the Intel IOMeter File Server Access Pattern
[global]
description=Emulation of Intel IOmeter File Server Access Pattern
randrepeat=0
filename=/root/test.dat
# IOMeter defines the server loads as the following:
# iodepth=1 Linear
# iodepth=4 Very Light
# iodepth=8 Light
# iodepth=64 Moderate
# iodepth=256 Heavy
iodepth=8
size=80g
direct=0
ioengine=libaio
[iometer]
stonewall
bs=4M
rw=randrw
[iometer_just_write]
stonewall
bs=4M
rw=write
[iometer_just_read]
stonewall
bs=4M
rw=read
"""
You can measure the virtual machine RSS usage on the hypervisor with:
virsh dommemstat <machine name> | grep rss
or if you are not using libvirt:
grep RSS /proc/<PID of qemu process>/status
When switching off the RBD client cache, all is ok again, as the
process does not use so much memory anymore.
There is already a ticket on the ceph bug tracker for this ([1]).
However I can reproduce that memory behaviour only when using qemu
(maybe it is using librbd in a special way?). Running directly 'fio'
with the rbd engine does not result in that high memory usage.
[1] http://tracker.ceph.com/issues/20054
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1701449/+subscriptions
next prev parent reply other threads:[~2018-10-01 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 6:09 [Qemu-devel] [Bug 1701449] [NEW] high memory usage when using rbd with client caching Nick
2017-07-03 8:12 ` [Qemu-devel] [Bug 1701449] " Markus Schade
2017-07-20 9:48 ` joconcepts
2017-09-29 8:55 ` James Page
2017-09-29 10:18 ` Nick
2018-10-01 19:23 ` Andreas Hasenack
2018-10-01 19:44 ` Jason Dillaman [this message]
2020-11-09 18:02 ` Thomas Huth
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=153842307795.2557.15891416982810791845.malone@wampee.canonical.com \
--to=dillaman@redhat.com \
--cc=1701449@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.