View Single Post
  #3 (permalink)  
Old May 18th, 2007, 21:29
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
 
Join Date: Jun 2006
Location: West Chester, PA
Posts: 847
Blog Entries: 7
Thanks: 53
Thanked 205 Times in 124 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Optimizing GC3 v5.0 Performance - Part 1

Arham,

Can you tell me what platform you're running on? There are memory limitations with the current 32-bit JDKs and OTM doesn't yet support (or work with) the newer 64-bit JDKs. Each platform has different memory limitations, and I believe the current limits are:
  • AIX - 3GB
  • HP-UX - 3GB
  • Linux - 2.5 GB
  • Solaris - 2GB
  • Win32 - 1.5GB
Of these, JRockit on Linux is by FAR the best performing, even though it doesn't support the largest heap. This is partially due to the massive optimizations that JRockit performs -- in fact a JRockit instance with a 2.5GB heap can consume nearly 4GB of total memory (heap + jvm process).

Another point - you're one of the first clients to use OTM with OAS and I caution you to test diligently. While OAS both performs and functions better than OTM on WebSphere, it doesn't support all of the functions, nor perform as well as OTM on WebLogic. Also, since it's a newer platform, it is considerably more buggy.

Let me know what platform you're running on and what volumes you're intending to run through and I can provide you with more detailed info.

Thanks!
--Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com
Reply With Quote