From: Stefan Priebe <s.priebe@profihost.ag>
To: Oliver Francke <Oliver.Francke@filoo.de>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Some findings on 0.48, qemu-1.0.1 eating up RDB-write-cache memory
Date: Mon, 09 Jul 2012 20:16:17 +0200 [thread overview]
Message-ID: <4FFB1FF1.4050308@profihost.ag> (raw)
In-Reply-To: <4FFAC001.4020503@filoo.de>
Am 09.07.2012 13:26, schrieb Oliver Francke:
> After doing some normal IOps testing with:
> spew -v --raw -P -t -i 5 -b 4k -p random -B 4k 2G /tmp/doof.dat
>
> so a 2G file, tested for IOps-performance with 4k blocks I get a pretty
> good value for 5x write/read-after-write:
Just be interested as i'm still trying to get good IOps values. Have you
tried with a 200GB File / whole block device?
Stefan
prev parent reply other threads:[~2012-07-09 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 11:26 Some findings on 0.48, qemu-1.0.1 eating up RDB-write-cache memory Oliver Francke
2012-07-09 18:16 ` Stefan Priebe [this message]
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=4FFB1FF1.4050308@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=Oliver.Francke@filoo.de \
--cc=ceph-devel@vger.kernel.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