× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2007

RE: Performance tuning of the IBM WAS Admin Server

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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.