Memory usage increased form 500MB to 4 GB after changing the tomcat process from 32 bit to 64 bit execution

["nagendra.raju@wipro.com" <na...@wipro.com>]

Hi All,
Problem statement: Memory usage increased form 500MB to 4 GB after changing the tomcat process from 32 bit to 64 bit execution
As tomcat memory has increased it is impacting available memory for other applications on server

o   Is this a bug ?

o   Earlier with 32bit it was running around 400MG, If we restrict the tomcat memory to 500GB for 64bit application will  it any impact on tomcat operations

Tomcat Version : Tomcat 7.0.73 on Solaris 11


Thanks & Regards
Nagendra Raju

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

Re: Memory usage increased form 500MB to 4 GB after changing the tomcat process from 32 bit to 64 bit execution

["André Warnier (tomcat)" <aw...@ice-sa.com>]

On 14.04.2017 10:36, nagendra.raju@wipro.com wrote:
> Hi All,
> Problem statement: Memory usage increased form 500MB to 4 GB after changing the tomcat process from 32 bit to 64 bit execution
> As tomcat memory has increased it is impacting available memory for other applications on server
>
> o   Is this a bug ?
>
> o   Earlier with 32bit it was running around 400MG, If we restrict the tomcat memory to 500GB for 64bit application will  it any impact on tomcat operations
>
> Tomcat Version : Tomcat 7.0.73 on Solaris 11
>

Maybe as a very first observation : it is not Tomcat that you changed. The Tomcat code has 
remained exactly the same. It is the Java JVM that was changed, from a 32-bit to a 64-bit 
version. So /that/ is the underlying reason for the memory usage increase, not Tomcat.
Read more on the topic : http://lmgtfy.com/?q=java+32-bit+vs+64-bit

(I recommend this one as a starter : 
http://howtodoinjava.com/for-fun-only/difference-between-32-bit-java-vs-64-bit-java/)

Thus, to respond to your first question : no, it is no a bug; or at least not a Tomcat bug.
About your second question : there is no such thing as a 64-bit application under Tomcat. 
All Tomcat applications are written in Java, and are ultimately run by the Java JVM. It is 
the JVM which determines if this uses, for example, 32-bit or 64-bit memory pointers, 
4-byte or 8-byte object references etc.
If you reduce the available memory for the Tomcat Heap, then, depending on the way the 
applications are written, this may cause more Memory Garbage Collections to occur in any 
given period of time.  Whether this really impacts your applications or not, is something 
which only you can measure and determine.
Try it, and look at the results.
Or add more memory to your server.
If you went from a 32-bit JVM to a 64-bit JVM, presumably you had a reason for doing that. 
Wat was the reason ? (And if there was no good reason, you can always go back).



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Memory usage increased form 500MB to 4 GB after changing the tomcat process from 32 bit to 64 bit execution

[Christopher Schultz <ch...@christopherschultz.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Nagendra,

On 4/14/17 4:36 AM, nagendra.raju@wipro.com wrote:
> Problem statement: Memory usage increased form 500MB to 4 GB after
changing the tomcat process from 32 bit to 64 bit execution

Any other changes? For example, changes to the heap configuration, stack
configuration, or any other memory-related parameters?

Please post your complete JVM launch command. If you use "catalina.sh"
or "startup.sh" to launch Tomcat, use "ps" to find out the effective
command and post that.

How are you measuring the "memory usage"?

> As tomcat memory has increased it is impacting available memory
> for other applications on server
> 
> o   Is this a bug ?

Almost certainly not.

> o   Earlier with 32bit it was running around 400MG, If we restrict 
> the tomcat memory to 500GB for 64bit application will it any
> impact on tomcat operations

You can only restrict the size of the various heaps. AFAIK, there is no
way to restrict the amount of native memory that the JVM uses.

> Tomcat Version : Tomcat 7.0.73 on Solaris 11

What JVM versions (32-bit and 64-bit)?

- -chris

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJY8QnDAAoJEBzwKT+lPKRYRQ0QAMc2mdwMwRmdp5Nh/9S7cVKW
2hSW3/v3nXcm0hWb6aq9e5UN9EqHQYZYIAu+Oil7aMwzQhS1blf4AZzcA/Zt1Mos
scinD9dNSsoAF+hdVz0zxyF/u/PpKiIQPgVuRJb12gZzDqvYcYHAph4U5T7bi89Y
eqKA+imc3ShWy3u4STDuu9RUEUqHuMUZ7efH8cDByUnwuHPDPYEdwcb5CWvimkWr
E15Z9JGNsaluUZfC6hD8cFbVtegoPGIjYRKqRY0bRXshJkGlFITk/W4m5wMDTvW7
Or9THmCgtgIPkd+hdCjqlJ4kjOe5eEGhW1Lk6UsQSEOItTx23+hUYQf6q6f+Y/2o
jWJoj/I2xo7pC3YptwK0eB3kI5ABaTfFOMJZ2IO0Dzp3QkVWg7nvLN2YFOG1P8Hz
6s82xP4GArx/nghaPK4IYwn3KaBbG4DHQWtND2w97PwcuE2x8qrnZce2LrQX/1lH
vwzK6wqyDWJ/jlJeZm18u+nKT7cBLLcF+KJVhrjXAuDGtRYVzSA0aqqePLScQYp+
pk2H4Qhn9+HU0FTw7sXC1lSQXpwukdigeFc3qLPAb68gGBAWWa5ywVXOqQ45XHpE
43Pp1AmU3EcUgz40ZXHr0Exfoa8afDRzx4mVjP+FY4bpy1jA7hca7OGMI62eAL63
g8+unU7dnSD9VTy/S9/q
=dmc3
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org