Jens Axboe

You're missing the most important big, WHY does it cause a performance drop when identify takes too long? The identify only happens on open, correct? And as far as I...

Is there someone opening the device while the test is running? If it's not a cached identify, then it's quite possible it'll quiesce the OS level queue and hence cause...

> And I agree that increasing waiting time is not the core solution. If the identifier ends slower than the increased time, the same problem will occur again. Exactly. So...

Can you turn that into a patch / PR? You already did all the work, and that would make our life easier.

I'd personally be fine taking a PR that cleans up that bit, but I have no interest in working on it myself. If external engines want their life to be...

Quick guess - it's compressing and writing out the latency logs. This is also why it's slower when you use the null engine, as you'll have a lot more entries...

My only worry on delaying the compression and write back of the logs is that it'll potentially tie up increasingly more memory as you go. But outside of that, it...

Right, mostly just thinking in terms of memory usage from the logs by that job. There are other things too, as we'd be preventing the job from exiting (maybe? we...

See the ```---max-jobs``` and ```--alloc-size``` options.

CC @damien-lemoal