Yes, Chris,
it depends on the type of data.
For example:
1) the elements of an array are addressed with 64 bit pointers;
2) on a x32 a long (32bit) is as large as a x64;
and so on....
By the way, what options for the JVM are you speaking about?
Domenico
----- Original Message -----
From: "Christopher Schultz" <ch...@christopherschultz.net>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Monday, February 08, 2010 5:22 PM
Subject: Re: max heap size on Windows server 64 bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Domenico,
On 2/4/2010 3:42 AM, Domenico Marzilli wrote:
It's normal to be forced to double the heap on migrating from x32 to x64
hw.
Just think to the pointer addressing , that is based on a 64bit
representation of the memory address, rather than a 32bit.
Er... maybe. Just because all pointers get twice as big doesn't mean all
data gets twice as big. And, there are options for the JVM that allow
the pointers to stay small, too :)
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktwOjQACgkQ9CaO5/Lv0PAdtACfQF4FKJ6223sTLc/9LFn43EBP
hOIAnR9yCd17enKq7rfQ9e2DYyAo4T+e
=krfG
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
