Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?

To: graphicsguru who wrote (239513)	8/29/2007 3:19:37 AM
From: muzosi	Read Replies (1) \| Respond to of 275872

The only situation where it could be bad is for code that relies on a large number of mutex locks to ensure correct serialization. But most good parallel code figures out ways to keep the mutex locks to a minimum, often by keeping separate writable copies of data in each thread. Code that relies heavily on mutexes generally performs very poorly. this is certainly true. but alas most non-(or lightly) threaded apps in the first porting will use mutexes heavily. writing parallel code is quite hard and doing it well is much harder. it'll take a while for these features to be relevant and in the mean time the solution which performs better with bad code will win.