• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Maximun Heap Size in WAS 7.0

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
-All,

I would like to know what is the Maximum heap size I can set for a JVM in WAS?
I appreciate you response.

Thanks,
San Ran
 
Ranch Hand
Posts: 446
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The maximum heap size allocation to any JVM is dependent on several parameters like:
1. Operating System
2. Processor Bit Size (16, 32, 64 etc)
3. Physical & Virtual Memory configured on the server.
4. Bit size of the JVM (32 bit JVM vs 64 bit JVM).
5. # of JVM processes running on the server.

Generally it is not advisable to throw large chunk of memory at the JVM as some folks try to solve software problems by throwing hardware at it.

I would suggest you start with a low number like 512m or 1024m and then try to increase in chunks of 1024M.

As a simple answer you can throw big number like 2g or 4b on 32 bit machines. JVM may reject the heap size giving some logical error.

Hope this helps.

 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic