QuicksearchDisclaimerThe individual owning this blog works for Oracle in Germany. The opinions expressed here are his own, are not necessarily reviewed in advance by anyone but the individual author, and neither Oracle nor any other party necessarily agrees with them.
|
Multitude of JVM - misinterpreted ;)Monday, July 12. 2010Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Partitioning an application into multiple 32 Bit JVMs is still a real world use case - unfortunately.
For example, in IBM WebSphere 6 (still the dominant version in large companies), there's not even support for 64 Bit VMs on Solaris Sparc. It's the Sun VM, all right, but you cannot replace it, because IBM requires the IBM customized version of the Sun VM (I think the ORB is one of the things that's different).
If one's workload is amenable to a 32-bit runtime environment, on all common and current processors running in 32-bit mode is faster than 64-bit mode. Seems like it's just good sense to retain that 3-7% performance rather than throw it away pointlessly.
Maybe, just maybe, when you need just bunch of 32-bit JVMs, each used with single CPU... you can use two dozens of PCs instead of a large SMP box?
I agree with Arnd. Another real world use case: Applications that do not scale with the number of cores. You get a log better performance by running a hand full of them in parallel for the same job on a multicore-system instead of running one big appserver instance. BTST - a lot...
For the moment you can only blame SPEC organization. The specification of SPECjbb2005 benchmark for now is that the overall result matters.
I agree with xysmith. If IBM runs the same on sigle JVM 64-bit, the score will be about 5% lower. Still a disaster for SPARC servers... we cannot do much about it. SPARCs are currently the slowest cores on market.
I assume it would be much slower than just the 5%. 5% is just the mininum impact for 64-bitness without compressed OOPs.
The impact of factoring out the interconnect between the procs is much larger. Running SPECjbb2005 in a single JVM on larger system would give interesting insights to the efficiency of the interconnect. Unfortunately there isn't such a result.
TPM seemed to get a particular fact incorrect in the story:
http://www.itjungle.com/tfh/tfh071210-story02.html "Oracle's T5440, a four-socket box using the Sparc T2+ processor running at 1.6 GHz and sporting eight cores and 32 threads per chip" If I remember correctly, the T5440 is using the SPARC T2+ processor sporting 64 threads per chip. http://en.wikipedia.org/wiki/UltraSPARC_T2 No where to comment, unnfortunately... I am looking forward to the T3 being released, however!!!
I stopped to expect factual correctness about Sun from TPM ... so i'm just writing about the fundamental problems ...
|
+1The LKSF bookThe book with the consolidated Less known Solaris Tutorials is available for download here
Web 2.0Contact
Networking xing.com My photos CommentsMon, 21.05.2012 04:44
Hi Greg,
With regards to IO
PS I have seen terrible result
s using a 60GB SATA2 SSD with
USB2.0 - USB2 really cho [...]
about ZFS Dedup Internals
Sat, 19.05.2012 09:50
There is no impact to boot/imp
ort times, as the DDT is loade
d as needed ... so the pool is
imported as fast as wit [...]
about Tracks
Tue, 15.05.2012 19:46
Very nice, I like the way the
eye is taken right into the pi
cture. Did you use any filter
s not to make the green [...]
Buttons![]() This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Germany License
![]() ![]() ![]() Blog Administration |