* Re: accuracy of btt result on btreplay?
2010-03-03 7:41 accuracy of btt result on btreplay? Xuekun Hu
@ 2010-03-03 14:05 ` Alan D. Brunelle
2010-03-04 1:37 ` Xuekun Hu
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Alan D. Brunelle @ 2010-03-03 14:05 UTC (permalink / raw)
To: linux-btrace
Hi Xuekun -
Not sure why they Q2Q N value is down 5%, but the AVG Q2Q is pretty
close - only 11msec (again, about 5%). After that, things are affected
by merge rates most likely - note that there were 262882 merges on the
first run whilst there were only 8970 on the second run. Perhaps you
could look at the blkparse output from both and get a feel for the vast
reduction in merges. [Any changes on the system between the runs?]
Regards,
Alan
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: accuracy of btt result on btreplay?
2010-03-03 7:41 accuracy of btt result on btreplay? Xuekun Hu
2010-03-03 14:05 ` Alan D. Brunelle
@ 2010-03-04 1:37 ` Xuekun Hu
2010-03-05 7:30 ` Xuekun Hu
2010-03-08 8:38 ` Xuekun Hu
3 siblings, 0 replies; 5+ messages in thread
From: Xuekun Hu @ 2010-03-04 1:37 UTC (permalink / raw)
To: linux-btrace
Hi, Alan
It should be no changes on the system.
I compared the per io dump info, and found the merges did decrease a
lot. Another interesting thing I found from the blkparse output is the
write requests has much more "WS" (synchronous) flag in the replay
run. Does the merges decrease due to the "S" flag?
Perhaps I need to tune the "-max-pkts"? In my case, to increase its
value to let more requests have more opportunities to merge?
BTW. I also tried replaying "dd" traces, and found the number of
merges also decreases.
Thx, Xuekun
On Wed, Mar 3, 2010 at 10:05 PM, Alan D. Brunelle <Alan.Brunelle@hp.com> wrote:
>
> Hi Xuekun -
>
> Not sure why they Q2Q N value is down 5%, but the AVG Q2Q is pretty
> close - only 11msec (again, about 5%). After that, things are affected
> by merge rates most likely - note that there were 262882 merges on the
> first run whilst there were only 8970 on the second run. Perhaps you
> could look at the blkparse output from both and get a feel for the vast
> reduction in merges. [Any changes on the system between the runs?]
>
> Regards,
> Alan
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrace" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: accuracy of btt result on btreplay?
2010-03-03 7:41 accuracy of btt result on btreplay? Xuekun Hu
2010-03-03 14:05 ` Alan D. Brunelle
2010-03-04 1:37 ` Xuekun Hu
@ 2010-03-05 7:30 ` Xuekun Hu
2010-03-08 8:38 ` Xuekun Hu
3 siblings, 0 replies; 5+ messages in thread
From: Xuekun Hu @ 2010-03-05 7:30 UTC (permalink / raw)
To: linux-btrace
Updates. I decreased/increased max-pkts to 1/16, however nothing
changed, still less merges in the replay run.
I think the "S" attribute for "write" should be the reason. First I
suspected the "S" attribute is brought by io_submit system call,
however I tested aio-stress tool which uses io_submit to send AIO
also. In the gathering traces, the write operations doesn't have "S"
attribute, however during replay, the "S" attribute happened again.
So I wonder where the "S" comes from? Does anyone have suggestions?
Thanks in advance.
Thx, Xuekun
On Thu, Mar 4, 2010 at 9:37 AM, Xuekun Hu <xuekun.hu@gmail.com> wrote:
> Hi, Alan
>
> It should be no changes on the system.
>
> I compared the per io dump info, and found the merges did decrease a
> lot. Another interesting thing I found from the blkparse output is the
> write requests has much more "WS" (synchronous) flag in the replay
> run. Does the merges decrease due to the "S" flag?
>
> Perhaps I need to tune the "-max-pkts"? In my case, to increase its
> value to let more requests have more opportunities to merge?
>
> BTW. I also tried replaying "dd" traces, and found the number of
> merges also decreases.
>
> Thx, Xuekun
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: accuracy of btt result on btreplay?
2010-03-03 7:41 accuracy of btt result on btreplay? Xuekun Hu
` (2 preceding siblings ...)
2010-03-05 7:30 ` Xuekun Hu
@ 2010-03-08 8:38 ` Xuekun Hu
3 siblings, 0 replies; 5+ messages in thread
From: Xuekun Hu @ 2010-03-08 8:38 UTC (permalink / raw)
To: linux-btrace
I think I found where the "S" flag was put for write IO request. In
the kernel function __blockdev_direct_IO(), every write request will
be tagged as "sync". Since btreplay uses O_DIRECT + AIO, which should
go into __blockdev_direct_IO.
So now my views on btreplay:
1. for write request, btreplay will decrease merge rates, thus impact
the latency etc.
2. for read request, btrecord may adjust "-max-pkts"/"-max-bunch-time"
to control the size of bunch to close to the real read IO merge rates.
Thx, Xuekun
On Fri, Mar 5, 2010 at 3:30 PM, Xuekun Hu <xuekun.hu@gmail.com> wrote:
> Updates. I decreased/increased max-pkts to 1/16, however nothing
> changed, still less merges in the replay run.
>
> I think the "S" attribute for "write" should be the reason. First I
> suspected the "S" attribute is brought by io_submit system call,
> however I tested aio-stress tool which uses io_submit to send AIO
> also. In the gathering traces, the write operations doesn't have "S"
> attribute, however during replay, the "S" attribute happened again.
>
> So I wonder where the "S" comes from? Does anyone have suggestions?
> Thanks in advance.
>
> Thx, Xuekun
>
^ permalink raw reply [flat|nested] 5+ messages in thread