Re: Performance Issues -- WEB400

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

On 8/7/2017 3:18 PM, Hohlen, Kent wrote:

Something in 7.2 behaves different then in 5.4 or we are missing a setting.

The first thing I think about is the memory allocation. Are the pools
the same size as they used to be?

WRKSBS
Look for QHTTPSVR.
Remember the subsystem pool number.
WRKSYSSTS
Look for that pool number (2 is *BASE).
Try your web app in 'slow' mode.
Wait 30 seconds to a minute.
What are the paging/faulting stats like?
Press F11 a few times to get a good picture.
Reset the stats.
Try your web app in 'fast' mode.
Wait 30 seconds to a minute.
What are the paging/faulting stats like?

Does anything stand out?

Performance tuning works best when there are records of settings from
when the system was working acceptably. We can't go into the past and
get them, but we can start capturing that intel now...

Is there some log that shows when a request hits the server and what job or program path a request takes? I'm trying to narrow down where the issue is.

You can turn up the logging level in the Apache server and check the
resulting log detail. Use the Admin console on port 2001/HTTPAdmin

You can also use this option to look at real time statistics.

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.