News for hackers. Stuff that matters.
Re:Libtorrent experience - the poor state of async disk IO by evmar on Friday October 26, 2012 @02:20PM (#4703484)
(Copy'n'paste of reddit comment:)

While it's true that the Windows API seems to be the best thought through, I was surprised to learn that the implementation may randomly fall back to synchronous IO in unpredictable ways, which (depending on the app, but likely for something that's attempting to juggle a lot of work like a bittorrent implementation) means you need a thread pool anyway.

http://neugierig.org/software/blog/2011/12/nonblocking-disk-...

Re:Libtorrent experience - the poor state of async disk IO by mey on Friday October 26, 2012 @02:48PM (#4703627)
Interesting, I've personally experienced this bug multiple times and always been surprised when it happens since Chrome is normally extremely responsive UI wise even when under load.
Re:Libtorrent experience - the poor state of async disk IO by derleth on Saturday October 27, 2012 @03:12AM (#4705634)
My experience is the opposite: When Chrome starts to hit the disk, it freezes, especially on startup.