RE: Performance tuning of the IBM WAS Admin Server

["Jones, John \(US\)" <John.Jones@xxxxxxxxxx>]

This applies to WAS instances but I don't see why it wouldn't apply to
the WAS admin server.

Moving WAS, specifically the QEJBAS5 subsystem for WAS 5.0, to a
separate memory pool will help.  WAS & the JVM are RAM pigs and you will
probably find a lot of paging/faulting going on as WAS and the JVM
compete with the other jobs on the system for RAM resources.  You'll
probably find DASD % Busy spiking are a result as well.

Once moved be sure to set the minimum RAM & threads (Max Active in
WRKSHRPOOL/WRKSYSSTS) to what you see WAS as using at run-time.
Minimally what it uses at start-up but ideally what it consumes at peak.

FYI Running JDPeopOracle's EnterpriseOne we've seen a single WAS/Java
job use over 13GB RAM.  IIRC we used DMPJVM to see the details.