<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 2, 2016 at 12:03 PM, Atin Mukherjee <span dir="ltr"><<a href="mailto:atin.mukherjee83@gmail.com" target="_blank">atin.mukherjee83@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one</p><div><div class="h5"><br>
On Jan 2, 2016 11:52 AM, "Vijay Bellur" <<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>> wrote:<br>
><br>
> On 12/30/2015 10:36 AM, Raghavendra Talur wrote:<br>
>><br>
>> This is not comprehensive data but some interesting bits<br>
>><br>
>> Average time taken for various commands in our .t files.<br>
>><br>
>> * glusterd - 2 second<br>
>> * gluster vol start/stop - 3 second<br>
>> * gluster vol set/info(any basic gluster cli command) -1 second<br>
>> * gluster mount - 2 second<br>
>> * gluster add brick - 2 second<br>
>> * gluster remove brick - 5 second<br>
>> * gluster rebalance start 5 second<br>
>> * gluster tier attach/detach - 6 second<br>
>><br>
>> The only other single command which takes 1+ second is sleep. Most of<br>
>> the other<br>
>> external commands we use in bash scripts are not that time taking.<br>
>><br>
>><br>
>> Hence,<br>
>><br>
>> 1. Don't stop/delete a gluster volume in .t file unless it is part of<br>
>> your test. Let the cleanup function handle that.<br>
>> 2. Don't call gluster vol info at the start of the test if not required<br>
>> 3. Merge as many tests as possible to reduce glusterd starts/vol starts<br>
>> and mounts.<br>
>> 4. Use sleep only if it is absolutely required.<br>
>><br>
>> You can use this bug <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1294826" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1294826</a><br>
>> to send patches to improve test times.<br>
>><br>
><br>
> Thank you! These are good set of steps that can help in reducing the overall time consumed for a regression test run. I also think the larger latencies observed in volume operations could be related to the the set of fsync()s involved in making configuration state durable in glusterd's store. It would be interesting to see if we can use a ramdisk for /var/lib/glusterd and check if the latencies would improve.<br></div></div>
That's a good suggestion. It'd definitely improve the latency.<br></blockquote><div><br></div><div>Tried this.</div><div>I saw improvement of 1 second with commands which took over 4 second. May be there is something else which is taking more time?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
><br>
> Regards,<br>
> Vijay<br>
><br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
<p></p>
</blockquote></div><br></div></div>