From: Jonathan Tripathy <jonnyt-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
To: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Windows IOPS Benchmark
Date: Thu, 30 Aug 2012 01:09:10 +0100 [thread overview]
Message-ID: <503EAF26.6020009@abpni.co.uk> (raw)
Hi Everyone,
I'm using bcache with a RAID1 pair of SSDs (for the cache) with a
MD-RAID10 spindle array for the backing device. On top of this is LVM.
This setup is used with the Xen Hypervisor. Bcache is formatted with a
sector size of 512 bytes.
If I use an LV for a Linux DomU, I get fantastic disk performance using
fio (about 23k random write). However, when I use IOMeter in a Windows
HVM DomU (with GPLPV drivers installed), my avg IOPS is around 4000. I
am using the "default" Access Specification. Am I doing something wrong?
Changing the number of workers doesn't seem to help.
Any advice is appreciated.
Thanks
next reply other threads:[~2012-08-30 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 0:09 Jonathan Tripathy [this message]
[not found] ` <503EAF26.6020009-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-30 0:13 ` Windows IOPS Benchmark Jonathan Tripathy
[not found] ` <503EB016.10603-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-30 12:48 ` David Rhodes Clymer
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=503EAF26.6020009@abpni.co.uk \
--to=jonnyt-nf8s+5hnwl710xsdtd+oqa@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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