qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: qemu block <qemu-block@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] coroutine pool memory usage
Date: Thu, 27 Aug 2015 11:26:41 +0200	[thread overview]
Message-ID: <55DED7D1.3020101@kamp.de> (raw)

Hi,

i was debugging increased memory footprint of qemu over the past time and found that the coroutine
pool heap usage can grow up to 70MB by just booting an Ubuntu Live CD. And those 70MB are never
freed.

Is this expected? Wouldn't it make sense to asynchronically throw some coroutines (or at least their stack)
away if there is no I/O?

Does anyone have a pointer to benchmarks of coroutine performance for NAS (iSCSI / NFS) with and without
freelist? I would think that it only has significant impact for local (SSD) storage?

Thanks,
Peter

             reply	other threads:[~2015-08-27  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  9:26 Peter Lieven [this message]
2015-08-27 15:23 ` [Qemu-devel] coroutine pool memory usage Paolo Bonzini
2015-08-27 15:28   ` Peter Lieven

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=55DED7D1.3020101@kamp.de \
    --to=pl@kamp.de \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).