From: Stefan Priebe <s.priebe@profihost.ag>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Gregory Farnum <greg@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD Hardware questions
Date: Thu, 28 Jun 2012 18:00:36 +0200 [thread overview]
Message-ID: <4FEC7FA4.3010307@profihost.ag> (raw)
In-Reply-To: <4FEC6C68.2030307@inktank.com>
Am 28.06.2012 16:38, schrieb Mark Nelson:
> On 06/28/2012 08:21 AM, Stefan Priebe - Profihost AG wrote:
>> While doing sequential writes i see pretty low CPU usage. Random writes
>> is the problem.
>>
>> Stefan
>
> It would be interesting to see where all your CPU time is being spent.
Correct - what do you need?
> What benchmark are you using to do the random writes?
in KVM VM:
export DISK=/dev/vda
fio --filename=$DISK --direct=1 --rw=randwrite --bs=4k --size=200G
--numjobs=50 --runtime=90 --group_reporting --name=file1
Stefan
prev parent reply other threads:[~2012-06-28 16:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 13:04 OSD Hardware questions Stefan Priebe - Profihost AG
2012-06-27 13:55 ` Mark Nelson
2012-06-27 14:55 ` Jim Schutt
2012-06-27 15:19 ` Stefan Priebe
2012-06-27 17:23 ` Jim Schutt
2012-06-27 17:54 ` Stefan Priebe
2012-06-27 18:38 ` Jim Schutt
2012-06-27 18:48 ` Stefan Priebe
2012-06-27 19:10 ` Jim Schutt
2012-06-27 19:14 ` Jim Schutt
2012-06-27 15:53 ` Mark Nelson
2012-06-27 17:59 ` Jim Schutt
2012-06-27 15:13 ` Stefan Priebe
[not found] ` <CAPYLRzj916kW=KLy3dMTVPJRoNtPMP_Ejz+YAxRUJ5jZc+HeMg@mail.gmail.com>
2012-06-27 15:28 ` Stefan Priebe
2012-06-27 16:00 ` Mark Nelson
2012-06-28 13:21 ` Stefan Priebe - Profihost AG
2012-06-28 14:38 ` Mark Nelson
2012-06-28 15:18 ` Alexandre DERUMIER
2012-06-28 15:33 ` Sage Weil
2012-06-28 15:45 ` Alexandre DERUMIER
2012-06-28 15:48 ` Jim Schutt
2012-06-28 21:25 ` Stefan Priebe
2012-06-29 11:37 ` Mark Nelson
2012-06-29 12:35 ` Stefan Priebe - Profihost AG
2012-06-28 16:01 ` Stefan Priebe
2012-06-28 16:00 ` 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=4FEC7FA4.3010307@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=mark.nelson@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.