64 bit JVM provided by Sun v/s 32 bit JVM provided WM.

raj_webmethods · March 30, 2006, 12:12am

Hello All,
We are running webMethods 6.5 on Solaris on a 32 bit JVM provided by webMethods.From webMethods 6.5 release we have an option of using 32 bit vs 64 bit JVM.we are thinking of using of pros and cons of using 64 bit JVM vs 32 bit.

Could some one explain pros and cons of 32 vs 64 bit JVM? which would be a better choice.

Thanks In Advance.

raj

raj_webmethods · March 30, 2006, 12:15am

Hello All,
Just to clarify that both 32 bit and 64 bit JVM is provided by webMethods not SUN.

Thanks,
Raj

reamon · March 30, 2006, 1:12am

The JDKs redistributed by wM for Solaris are from Sun. Sun 1.4.2_07.

reamon · March 30, 2006, 1:18am

[url]http://72.14.203.104/search?q=cache:--4T7ZHMLZQJ:escher.elis.ugent.be/publ/Edocs/DOC/P106_004.pdf+jvm+32-bit+64-bit+vs&hl=en&gl=us&ct=clnk&cd=4[/url]

Shows that a 64-bit JVM uses more resources and performs a smidge slower than a 32-bit JVM.

wMusers.Com1 · April 21, 2006, 12:55am

From the webMethods Technical Report “Hardware, JVM, and Operating System Performance Tuning Recommendations” dated November 2005 (Version 1.0)

64 bit JVMs
When processing very large documents, 64 bit JVMs (which require 64 bit operating systems and 64 bit hardware) offer a significant functional advantage, because they can keep more data in memory. As a result, webMethods highly recommends 64 bit hardware/software for environments that require very high volumes and/or very large documents, in particular where the concurrent memory requirements are larger than approximately 1.5GB.

Customers who are heavy users of the SAP and/or the WebSphere MQ adapters should particularly consider this avenue due to the potential for instability of the underlying, vendor provided, native code libraries when memory limits are exceeded.

Customers who do not need this amount of memory for the lifecycle of their production projects, should use 32 bit JVMs on either 32 or 64 bit hardware.
This will avoid incurring the additional cost of the 64-bit addressing, as well as avoiding the potential for an approximate 5% performance degradation due to the additional overhead (caused by the enlarged memory management overhead of the JVM and operating system).