Some people consider tuning the performance of Java Virtual Machines (JVMs) in an E-Business Suite environment to be more of an art than science. These comments usually result because of the large number of factors that may be considered, factors that are sometimes difficult to quantify.
Adding to the existing material available to help you perfect your art, our E-Business Suite Performance Group released a short whitepaper late with some tips:
- Guidelines to setup the JVM in Apps 11i (Metalink Note 362851.1)
- The number of recommended users per JVM
- The number of recommended JVMs per CPU
- Heap configuration tips for OACoreGroup, with guidelines for Forms Servlet mode and Configurator use
- Recommended techstack patches
- Master Class in Apps 11i Performance Tuning
- Using JConsole to monitor Apps 11i JVMs
- Configuring Middle-Tier JVMs for Applications 11i
- Investigating java.lang.OutOfMemoryError with Apps 11i Middle Tier JVMs
Comments (2)
Hello
I have asked for some clarification of note:362851.1 and thought I would also add the update to the blog.
1:- Where did the recommendation "There should be no more than 1 active JVM per CPU (ideally, there should be 1 JVM per 2 CPUs)" come from?
I can't find any evidence to back this up and Im not sure this is correct in all cases (I could agree for configurator or very large JVM's). I agree more with the statement in "http://blogs.oracle.com/schan/2006/08/01" of 2 JVM's per CPU, but even then I have seen more running perfectly fine on some of the faster CPU's. Given the statement above the middle tiers would need to be specced similar to the database tier if the customer is not using cheap Linux boxes.
2:- Could the note also be updated with a rough number of users per JVM as per
http://blogs.oracle.com/schan/2006/08/01
Cheers
Colin
Posted by Colin Parry | February 19, 2007 12:35 PM
Posted on February 19, 2007 12:35
Nice post Steven.
Sam
www.appsdbablog.com
Posted by Sam | February 22, 2007 1:31 AM
Posted on February 22, 2007 01:31