From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: Add support for jemalloc
Date: Tue, 23 Jun 2015 10:57:03 +0200 [thread overview]
Message-ID: <55891F5F.7000607@redhat.com> (raw)
In-Reply-To: <1524231966.526873.1435047769860.JavaMail.zimbra@oxygem.tv>
On 23/06/2015 10:22, Alexandre DERUMIER wrote:
> > What is the peak memory usage of jemalloc and tcmalloc?
>
> I'll try to use an heap profiling to see.
> Don't known if "perf" can give me the info easily without profiling ?
You can try using or modifying this systemtap script:
https://sourceware.org/systemtap/examples/process/proctop.stp
Paolo
next prev parent reply other threads:[~2015-06-23 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 10:56 [Qemu-devel] [PATCH] configure: Add support for jemalloc Alexandre Derumier
2015-06-20 5:55 ` Alexandre DERUMIER
2015-06-23 1:52 ` Fam Zheng
2015-06-23 7:57 ` Paolo Bonzini
2015-06-23 8:22 ` Alexandre DERUMIER
2015-06-23 8:57 ` Paolo Bonzini [this message]
2015-06-23 9:10 ` Alexandre DERUMIER
2015-09-07 20:36 ` Paolo Bonzini
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=55891F5F.7000607@redhat.com \
--to=pbonzini@redhat.com \
--cc=aderumier@odiso.com \
--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 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).