Java multi CPU capabilities

Christopher Browne cbbrowne-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Thu Aug 29 04:46:48 UTC 2013


The fact that the common JVMs are expected to behave properly on
Certain Operating Systems that don't much like forking processes puts
a certain amount of "crimp" in this, although I don't see people
complaining too much that you need to use fork() in order to get the
average C application to use multiple CPUs...

In practice, I'm not sure that many users terribly much *care* if a
single Java application harnesses all the CPUs on their systems; that
tends to get covered nicely by such additional factors as:

a) Composing a broader service using multiple Java applications;
b) Making the system easier to scale up by having multiple instances
of interesting Java applications

As soon as you do those things, you spatter the system with a bunch of
processes, and harness as many CPUs as you want to.

It's a pretty common strategy to attain parallelism by partitioning
problems so that you can throw it against multiple physical servers;
that strategy works perfectly well at splitting across CPUs.

If you choose a supremely monolithic implementation strategy for your
system that makes that nearly impossible, I'm not sure I'd consider
that Gosling's problem.
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list