On Sun, Jun 20, 2010 at 1:44 PM, Christian Brunner <chb@xxxxxx> wrote: > Hi Yehuda, > > while running tests with qemu-io I've been experiencing a lot of > messages when running a large writev request (several hundred MB in > a single call): > > 10.06.20 22:10:07.337108 b67dcb70 client4136.objecter pg 3.437e on [0] is laggy: 33 > 10.06.20 22:10:07.337708 b67dcb70 client4136.objecter pg 3.2553 on [0] is laggy: 19 > [...] > > Everything is working fine, though. I think that the large number of > queued requests is the cause for this behaviour and I would propose to > delay futher requests (see attached patch). > > What do you think about it? It seems that the osd is lagging behind. The usleep might work for you as you avoid the pressure, but it's also somewhat random and will probably hurt performance on other setups. I'd rather see a configurable solution that lets you specify a total in-flight bytes or some other resizable window scheme. > > Another question: I there a way to figure out max_osd through librados? Not currently. Thanks, Yehuda -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html