pcp
[Top] [All Lists]

Re: pmlogger -u questions

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: pmlogger -u questions
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Thu, 17 Apr 2014 18:51:50 -0400
Cc: Nathan Scott <nathans@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <53505571.6050900@xxxxxxxxxxxxxxxx>
References: <01e901cf56df$4ce97de0$e6bc79a0$@internode.on.net> <534B4330.1060008@xxxxxxxxxxxxxxxx> <y0meh104nvl.fsf@xxxxxxxx> <534C4FF4.5000304@xxxxxxxxxxxxxxxx> <20140414212551.GK14108@xxxxxxxxxx> <534C6531.6050502@xxxxxxxxxxxxxxxx> <155006091.5545657.1397518977813.JavaMail.zimbra@xxxxxxxxxx> <20140415002952.GM14108@xxxxxxxxxx> <216112516.5558630.1397522268210.JavaMail.zimbra@xxxxxxxxxx> <53505571.6050900@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi, Ken -

> I have completed the first round of this work ... as usual the final 
> implementation is a little messier than first expected ...

Looks good!

> [...]
>                         CPU     #writes Avg write size
>                         (sec)           (bytes)
> short - 3.9.2           1.15      142    3946
> short - new I/O         1.30    10004      56
> [...]

It would be informative to know how this translates to disk i/o.  We
don't use O_SYNC or fsync at this point, so it would be nice to be
reassured that we're not triggering many more physical I/Os than
before.  (We'd just be pushing buffering to the kernel.)


- FChE

<Prev in Thread] Current Thread [Next in Thread>