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. It's just that they
are *much more likely* to cause trouble on a multi-CPU system. It's
common to have bugs that show up once every few weeks on a single CPU, but
happen almost every time you run your program with two CPUs.
So testing on a dual-core or dual-CPU system is a good idea even if
your target hardware only has one CPU. It's a good way to catch some of
those hard-to-reproduce bugs.
Peter
_______________________________________________
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
