From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <5463D32C.9070804@kernel.dk> Date: Wed, 12 Nov 2014 14:37:48 -0700 From: Jens Axboe MIME-Version: 1.0 Subject: Re: Fio 2.1.14 released References: <54627C44.3080909@kernel.dk> <5462B6B0.3010003@kernel.dk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: Matthew Eaton Cc: "fio@vger.kernel.org" List-ID: On 11/12/2014 02:36 PM, Matthew Eaton wrote: >> It should all be as fast as it could be before. The issue fixed above is >> when we wanted the disk util thread to exit, we set a done flag and just >> waited for it to wakeup as, which it did a few times per second. Now we use >> regular condvars, so it'll wake and exit immediately. So disk_util=0 should >> not change more than a msec or so :-) >> >> That said, if you do find things where it seems to start or stop slower than >> it should, let me know. But as far as I know, it's all properly driven now. >> >> -- >> Jens Axboe >> > > Thanks! Just to follow up, I wrote a test script looping 20 > iterations of fio and tested 2.1.12 vs 2.1.14. > > 2.1.14 consistently finished ~2.7 seconds faster than 2.1.12, which I > think is great for only 20 iterations. That sounds reasonable. That's 135msec per iteration, which is roughly what we'd expect the average wait time to be (250msec / 2). -- Jens Axboe