× 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.



Last Thursday, I posted to the Java-400 List (and never heard back):

(Note that I originally had systems "A" and "J" transposed; "A" is the one that's having trouble)

We have a couple of Tomcat installations on customer boxes. Both are running in subsystems, with private pools, and both are running in Java 8 JVMs with starting heap 4096 and max heap 5120.

A WRKSYSSTS at Customer "J," with some 60 users connected to our webapp, is showing

 7168.00      2.53     500     .0     .0    3.4    6.2

for the private pool, while at Customer "A," with only around 44 users connected to the same webapp, is showing

 7125.00      1.11     200     .3    2.0   66.4  282.1

The non-DB page-faulting seems extraordinarily high.

Anybody got a clue what could be going on here?

Some more information:

1. Both System "A" and System "J" show GC happening roughly every 30-50 seconds, but I get the general impression that it's more effective on "J" than on "A."

2. On "A," if I look at the Java threads, most of the GC slave threads show Total CPU in a range from 5.2 to 5.5, but Aux I/O around 5700-6600 per thread. Conversely, on "J," the GC slave threads show Total CPU in the range from 148-149, but Aux I/O mostly zero, with none above 3.

Anybody got a clue what could be going on here?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.