Linked by Thom Holwerda on Fri 9th Sep 2011 15:17 UTC
Permalink for comment 489240
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2005-11-02
Now now, be nice.
I didn't spout off ridiculous "ME TOO"isms. I am relating my experiences and data I collected by observation over the course of many months. Symantec AV is pretty crap as well, of course, and this made things worse on days when it was running, but the overall effect was not altered. Just to be very clear: I observed the same pattern of slowness and speedup even without symantec grinding the disks horribly.
I'd like to address this point specifically, because you greatly misunderstand me. I read on LWN a Linux kernel developer talking about **LINUX**. In his opinion Linux has a bug if it cannot cope better with "A bunch of IO heavy tasks started simultaneously" than it can with "The same tasks started in sequence." He was saying that Linux should do better than the user, always, in scheduling IO or it's a bug in Linux. He never mentioned Windows.
What **I** did was begin thinking about the differences in the way I observed Linux and Windows reacting to disk contention, which lead me to run some experiments, which lead me to the conclusion that I began with above: Windows sucks at scheduling IO.
Edited 2011-09-12 20:09 UTC