-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
I've been thinking about the recent discussion(s) about 32-bit versus
64-bit performance on 64-bit hardware and I have a simple question:
what's the best deployment strategy for a Java webapp that doesn't
require *huge* amounts of memory, yet wants to maybe use more than ~1.5GiB?
Sine pretty much all current hardware is 64-bit, both 64-bit OS and
64-bit JVM are options. If running on a 32-bit OS, only 32-bit JVM is an
option. So the options are as follows:
1. 32-bit OS, 32-bit JVM
Pros: runs fast
Cons: OS can access large amount of memory, but JVM can only access
~1.5GiB
2. 64-bit OS, 32-bit JVM
Pros: OS runs somewhat slower, but JVM gets access to a bigger heap(?)
Cons: Cannot use *huge* heaps
3. 64-bit OS, 64-bit JVM
Pros: Access to obscene amounts of memory
Cons: Some slower performance for everything
Do I have that right? Specifically, can a 32-bit JVM on a 64-bit OS
allocate a larger heap than a 32-bit JVM on a 32-bit OS?
We are going into a production upgrade cycle and I'd like to plan for
the OS type: if we get no benefit from running a 64-bit OS then I won't
bother installing one.
Thanks,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1+Sc4ACgkQ9CaO5/Lv0PAnogCgnrDRzF7rvSNMP+FzCm9dNR5I
//EAn2X5OpI3qqvhxaIeRw61JIRvmqq8
=t307
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
