Question

I recently watching this video on Google Chrome with great interest. It explains that Google Chrome uses one thread for IO, one for opening files and one for intermodule communication.

I think I may be able to use something similar for my own – currently quite messy – application.

I wondered if there were any good articles on best-practices or patterns for such threaded divisions of tasks?

Answer 1

Any time your application has tasks that can be divided into distinct groups, it’s a candidate for multi-threading. Be warned that it’s a dangerous game, though – for every article you can find about the advantages, there are two about getting bitten by a multi-threading implementation – it can create bugs that only occur in certain configurations (on the users computers), or worse, can’t be duplicated in the debugger because the act of slowing down execution is enough to cause the bug to fail to appear (race conditions are notorious for this behavior).

That warning aside, multi-threading can be a huge boost to both the actual and the perceived performance of your application. These are .NET specific, but give a general primer explaining the advantages of background threads and keeping your UI responsive:

• http://msdn.microsoft.com/en-us/magazine/cc300429.aspx
• http://www.businessanyplace.net/?p=threads