As others have posted, a multi-CPU system can expose concurrency
bugs in your code that cannot cause trouble on a single CPU/core
system. If your users
I would amend that slightly: I've never heard of a concurrency
bug that *cannot* cause trouble on a single CPU system.
Well, you can easily figure out such a scenario. For instance, I have
code that instantiates a set of worker threads whose size is equal to
the number of processors in the system - this is to exploit all of
the computing power in the system. Well, I'm not experiencing any
kind of concurrency problem since the code of each worker is simple,
but it's clear that in a single CPU scenario I have a single thread
that cannot deadlock with itself, while in a multiple CPU scenario I
have multiple threads that could.
I agree that in most case it's just a matter of increased risk.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
