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. |
...