From: Josh Durgin <josh.durgin@inktank.com>
To: Greg Farnum <greg@inktank.com>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
Wido den Hollander <wido@widodh.nl>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: how to free space from rados bench comman?
Date: Thu, 24 May 2012 11:05:57 -0700 [thread overview]
Message-ID: <4FBE7885.6080200@inktank.com> (raw)
In-Reply-To: <986F41761DD1467EA38C8C853CFE8160@inktank.com>
On 05/24/2012 10:55 AM, Greg Farnum wrote:
> On Thursday, May 24, 2012 at 1:51 AM, Stefan Priebe - Profihost AG wrote:
>> Am 24.05.2012 10:22, schrieb Wido den Hollander:
>>> On 24-05-12 09:38, Stefan Priebe - Profihost AG wrote:
>>>>
>>>> ~# rados -p data ls|wc -l
>>>> 46631
>>>
>>>
>>>
>>> That is weird, I thought the bench tool cleaned up it's "mess".
>>>
>>> Imho it should cleanup after it's done, but there might be a reason why
>>> it's not. Did you abort the benchmark or did you let it do the whole run?
>>
>>
>> No it doesn't BUG?
> It doesn't because you might want to leave around the data for read benchmarking (or so that your cluster is full of data).
> There should probably be an option to clean up bench data, though! I've created a bug: http://tracker.newdream.net/issues/2477
Why not have the read benchmark write data itself, and then benchmark
reading? Then both read and write benchmarks can clean up after
themselves.
It's a bit odd to have the read benchmark depend on you running a write
benchmark first.
Josh
next prev parent reply other threads:[~2012-05-24 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 7:01 how to free space from rados bench comman? Stefan Priebe - Profihost AG
2012-05-24 7:28 ` Wido den Hollander
2012-05-24 7:38 ` Stefan Priebe - Profihost AG
2012-05-24 8:22 ` Wido den Hollander
2012-05-24 8:51 ` Stefan Priebe - Profihost AG
2012-05-24 17:55 ` Greg Farnum
2012-05-24 18:05 ` Josh Durgin [this message]
2012-05-24 18:14 ` Greg Farnum
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=4FBE7885.6080200@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=s.priebe@profihost.ag \
--cc=wido@widodh.nl \
/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.