Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for December 5, 2013
Deadline scheduling: coming soon?
LWN.net Weekly Edition for November 27, 2013
ACPI for ARM?
LWN.net Weekly Edition for November 21, 2013
Single-threading not considered harmful
Posted May 12, 2011 1:57 UTC (Thu) by Trelane (guest, #56877)
Posted May 12, 2011 15:47 UTC (Thu) by kamil (subscriber, #3802)
Posted May 12, 2011 15:52 UTC (Thu) by Trelane (guest, #56877)
Posted May 19, 2011 9:11 UTC (Thu) by renox (subscriber, #23785)
Maybe multi/single-tasking would be better terms?
Posted May 22, 2011 10:47 UTC (Sun) by kplcjl (guest, #75098)
The problem is recognizing when a dedicated single process is the best answer to your problem or when multiple threads on the same server would be best. Generally, when your problem is data driven, the multiple thread solution would be better and when your problem is cpu intensive, a single thread dedicated to solving the problem combined with a data storage mechanizm so multiple servers can attack several individual problems concurrently may be the way to go.
This article seems to cover the situation where one of those solutions fit and therefore it becomes the "best" solution for every situation. It doesn't seem to apply to dumb coding mistakes that make good design go bad. For instance, I saw one case where it should have used "-" instead of "+" in one place of a mathematical equation. It took me a week and a half to convince the manager there was a mistake in the equation.
Posted May 22, 2011 11:08 UTC (Sun) by kplcjl (guest, #75098)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds