Bigger iron has been at 64-512 TB for a while:
http://www.cray.com/blog/the-power-of-512-terabytes-of-share...
http://www.enterprisetech.com/2014/10/06/ibm-takes-big-workl...
Or significantly higher if you don't restrict yourself to single-system-image, shared memory machines - there are at least 2 1300-1500 TB systems on the Top 500 list.
Not using the out of the box solutions. But while I haven't done this personally my understanding is Azul Zing will allow you to efficiently use multi TB heaps in Java.
Java can address 32GB heaps with compressedoops flag enabled. After that flag is off, you can address as much as 64 bits will allow.
http://stackoverflow.com/questions/2093679/max-memory-for-64...
Do a little research before implying that there's no way that Java can address gigantic heaps.
Re:AWS X1 instances – 1.9 TB of memory
by cstejerean on Wednesday May 18, 2016 @02:19PM
(#11724360)
You can but garbage collection will kill your performance for very large heaps. You either end up needing to use off heap memory to take it out of scope for garbage collection or using many small JVMs with more reasonable sized heaps.
I wasn't implying or assuming anything, I was genuinely asking... I'm more familiar with windows, than other OSes, but iirc, windows apps can only get 4GB per process. (Maybe that was just 32bit windows apps).
Re:AWS X1 instances – 1.9 TB of memory
by Kristine1975 on Wednesday May 18, 2016 @02:08PM
(#11724225)
Just 32bit apps. 64bit apps can go much higher.
I was incorrect... Then again, I've never needed to address more than a couple gb of ram.
Still really cool to see something like this, I didn't even know you could get close to 2TB of ram in a single server at any kind of scale.