qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, "Zhang,
	Haozhong" <haozhong.zhang@intel.com>
Subject: Re: [Qemu-devel] Question about vNVDIMM file format
Date: Wed, 18 May 2016 18:36:33 +0100	[thread overview]
Message-ID: <20160518173633.GG1683@redhat.com> (raw)
In-Reply-To: <573C1414.1050608@linux.intel.com>

I thought you might be interested in some performance results, "hot
off the presses".

With DAX enabled, I see the following messages in the guest kernel
logs, which I assume means it is working:

[    0.469364] EXT4-fs (pmem0): DAX enabled. Warning: EXPERIMENTAL, use at your own risk
[    0.469932] EXT4-fs (pmem0): mounting ext2 file system using the ext4 subsystem
[    0.470682] EXT4-fs (pmem0): mounted filesystem without journal. Opts: dax

Enabling vNVDIMM + ext4.ko + DAX for the libguestfs appliance[1] root
disk improves our boot+shutdown performance measure[2] by between 20
and 30 milliseconds, which is about 5% faster at the moment.

I also wanted to know if memory usage is reduced.  I ran `free -m'
inside a freshly booted appliance.

Without DAX:

$ free -m
              total        used        free      shared  buff/cache   available
Mem:            485           3         451           1          30         465
Swap:             0           0           0

With DAX:

$ free -m
              total        used        free      shared  buff/cache   available
Mem:            485           3         469           1          12         467
Swap:             0           0           0

I also wanted to know if qemu's memory usage is reduced.  I captured
the rusage.ru_maxrss of the qemu subprocess with and without DAX.  The
difference is only about 5 MB, which doesn't seem like very much to
me.  Perhaps I'm measuring this wrong.

If you have better suggestions for measuring memory usage, please let
me know.

Rich.

[1] http://libguestfs.org/guestfs-internals.1.html#architecture
[2] http://libguestfs.org/guestfs-performance.1.html#baseline:-starting-the-appliance

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

  parent reply	other threads:[~2016-05-18 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 15:04 [Qemu-devel] Question about vNVDIMM file format Richard W.M. Jones
2016-05-16 16:53 ` Stefan Hajnoczi
2016-05-16 18:25   ` Richard W.M. Jones
2016-05-18  7:04     ` Xiao Guangrong
2016-05-18  8:11       ` Zhang, Haozhong
2016-05-18 10:50       ` Richard W.M. Jones
2016-05-18 17:36       ` Richard W.M. Jones [this message]
2016-05-16 17:39 ` Xiao Guangrong

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=20160518173633.GG1683@redhat.com \
    --to=rjones@redhat.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=haozhong.zhang@intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).