Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Simon Hughes

Simon Hughes sjh37 Software should not break. It should just work. Forever. No matter what...

Niner since 2008

Lead developer at www.bybox.com Love multi-threading and design patterns. Guru at C++, C# and SQL.
  • endpoint.tv - PDC Hands On Lab Cast - Lab 6 - Deploy and Manage Workflow Services

    Really like the executive overview without having to sit for an hour to go over every detail. Spot on.
  • Mark Russinovich: Inside Windows 7

    I'd like windows to not do a context swtich on a thread when its doing disk i/o. i want it to hold onto the thread for say 500ms, instead of 20ms as this gives the disk more time to read/write.

    If each thread is accessing a file, the whole thing slows down to a crawl as the hard disc read head has to jump to each file every 20ms. It would be MUCH better if the operating system could allocate more time to read a file before it allowed a context switch. say 500ms. that would allow more data to be retrieved from the hard disc, less head thrash, less time waiting for the head to move, and performance would go up greatly.

    Just try creating 2 or more zip archives at the same time, then time it again but only doing 1 at a time. Winrar has a feature where it will wait (probably using a global mutex) for other winrar windows to finish before the next one starts.

    You can context switch CPU threads till the cows come home, but a phsical device needs more time to read/write when the head arrives.

  • Parallel Computing Platform: An Integrated Approach to Tooling

    You have to be careful with parallel execution when it comes to disk I/O.
    If each thread is accessing a file, the whole thing slows down to a crawl as the hard disc read head has to jump to each file every 20ms. It would be MUCH better if the operating system could allocate more time to read a file before it allowed a context switch. say 500ms. that would allow more data to be retrieved from the hard disc, less head thrash, less time waiting for the head to move, and performance would go up greatly.

    Just try creating 2 or more zip archives at the same time, then time it again but only doing 1 at a time. Winrar has a feature where it will wait (probably using a global mutex) for other winrar windows to finish before the next one starts.

    You can context switch CPU threads till the cows come home, but a phsical device needs more time to read/write when the head arrives.