From: Stefan Priebe <s.priebe@profihost.ag>
To: Gregory Farnum <greg@inktank.com>
Cc: Sage Weil <sage@inktank.com>, Andrey Korolyov <andrey@xdel.ru>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: rbd export speed limit
Date: Wed, 13 Feb 2013 22:43:33 +0100 [thread overview]
Message-ID: <511C0905.7070509@profihost.ag> (raw)
In-Reply-To: <CAPYLRzhwhWjakVc2Ec8jP-8e+7VOB5eqDf63yCCLL2fxFHJ0-w@mail.gmail.com>
HI Greg,
Am 13.02.2013 21:38, schrieb Gregory Farnum:
>> Sorry it's MB - so the SSDs get fully utilized meased via /proc/diskstats .
>>
>>> I'm wondering if this is a lack of punch support on the kernel..
>>
>> I'm using 3.7.7 running XFS.
>
> Sounds like maybe the client trim is ending up issuing a truly
> ridiculous number of truncate or trim operations from librbd to the
> OSDs?
Yes for every single unused disk block ;-(
> Like one for every RADOS block that could exist, or possibly
> even for each VM disk block? (Perhaps not; I'm not sure how trim got
> implemented.)
I'm pretty sure Disk block...
> FWIW a full fstrim is not generally an operation you can really do in
> the background even on a real desktop...so if running it one one or
> several VMs makes the cluster unusable for all of them, that's a
> problem, but if it only causes IO trouble for the one which is
> trimming that'd be not ideal but less of an issue.
Yes if you can control this yes if you have no access to the client
machines no... or you can just disable trim support - but it's a nice
feature for provisioning...
Greets,
Stefan
next prev parent reply other threads:[~2013-02-13 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 20:22 rbd export speed limit Stefan Priebe
2013-02-12 20:45 ` Andrey Korolyov
2013-02-13 7:54 ` Stefan Priebe - Profihost AG
2013-02-13 16:13 ` Sage Weil
2013-02-13 19:25 ` Stefan Priebe
2013-02-13 20:21 ` Sage Weil
2013-02-13 20:27 ` Stefan Priebe
2013-02-13 20:38 ` Gregory Farnum
2013-02-13 21:43 ` Stefan Priebe [this message]
2013-02-21 7:53 ` Andrey Korolyov
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=511C0905.7070509@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=andrey@xdel.ru \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=sage@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.