| Panel |
|---|
As of Nov 2016 I have am no longer endorsing or providing support for 32-bit Java on 64-bit Ubuntu. Though I have not had a chance to do performance testing, with Cloud computing, lack of documention on 32-bit Java, and hopefully Oracle has continued to tune for 64-bit, it's time to move on. |
One problem with 64-bit Java is the amount of Memory it occupies:
- As explained by Oracle, "... every native pointer in the system takes up 8 bytes instead of 4".
- Also, we have observed that when a Java Application has access to a large amount of memory, the application gets bogged down when garbage collection occurs.
As of 2011 we feel that the majority of application profiles we have encountered do not require 64-bit Java as they often do not take advantage of using more than than 1-2GB of memory. Also, we have observed that when a Java Application has access to a large amount of memory, the application gets bogged down when garbage collection occurs. As explained by Oracle, "... every native pointer in the system takes up 8 bytes instead of 4".
| Note |
|---|
This has improved due to newer algorithms such as concurrency, parallelization and generational collection. However we observe there is still significant impact. |
...
| Warning |
|---|
More details explaining the mechanics can be put here or linked in another document. |
Good review of difference differences and pros and cons - http://java.dzone.com/articles/should-i-use-32-or-64-bit-jvm