From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@newdream.net>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Improving latency and ordering of the backfilling workload
Date: Mon, 15 Dec 2014 18:09:57 +0100 [thread overview]
Message-ID: <548F15E5.2030304@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1412150841220.5263@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
Hi Sage,
On 15/12/2014 17:44, Sage Weil wrote:
> On Mon, 15 Dec 2014, Loic Dachary wrote:
>> Hi Sam,
>>
>> Here is what could be done (in the context of http://tracker.ceph.com/issues/9566
>> ), please let me know if that makes sense:
>>
>> * ordering:
>>
>> * when dequeuing a pending local reservation, chose one that contains
>> a PG that belongs to the busiest OSD (i.e. the OSD for which there are
>> more PGs waiting for a local reservation than any other)
>
> I'm worried the reservation count won't be an accurate enough proxy for
> the amount of work the remote OSD has to do.
Are you thinking about taking into account the number and size of objects in a given PGs ? The length of the local reservation queue accurately reflects the number of PGs that need work (because the length of the reservation queue is not bounded). But it does not reflect the content of the PGs at all, indeed.
It would be very easy to
> piggyback some load information on the heartbeat messages which we should
> already be exchanging with anyone we would backfill with.
>
> If we go down that path, there are a bunch of patches in the wip-read-hole
> series that lay useful groundwork. Getting that branch into shape
> is the next big item after I finish the current batch of pull
> requests.
Would you mind telling me which of https://github.com/ceph/ceph/commits/wip-read-hole commits are relevant ? I assume https://github.com/ceph/ceph/commit/ee72f699e236371a5b8651cd900013a2bd2227fb is to some extent.
Cheers
>> * when sending a remote reservation request, set the priority to
>> reflect the total number of pending PG (absolute workload) and the
>> number local pending PG for the destination OSD (workload queued locally
>> for the remote OSD)
>> * on the receiving side, the priority of the remote reservation
>> request makes sure the busiest OSD gets a remote reservation before the
>> others
>>
>> * reducing latency:
>>
>> * if there are N pending remote reservations, reject a remote
>> reservation request instead of queuing it so that the local reservation
>> can be used instead of waiting.
>>
>> Cheers
>>
>> --
>> Lo?c Dachary, Artisan Logiciel Libre
>>
>>
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-12-15 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 14:24 Improving latency and ordering of the backfilling workload Loic Dachary
2014-12-15 16:44 ` Sage Weil
2014-12-15 17:01 ` Pavan Rallabhandi
2014-12-15 17:09 ` Loic Dachary [this message]
2014-12-15 17:20 ` Sage Weil
2014-12-15 17:48 ` Loic Dachary
2014-12-15 18:03 ` Sage Weil
2014-12-15 18:13 ` Loic Dachary
2014-12-18 0:54 ` Samuel Just
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=548F15E5.2030304@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.