Even though you said you're gotten your performance problem solved, one other thing that can make the initial hit take a long time is the amount of memory dedicated to the HTTP server (this can also affect WebSphere and Tomcat). If you're running this in a mixed workload box, running the web stuff in its own ASP with dedicated memory will help with performance since other jobs running will not cause those service's memory to be swapped out. If you see a lot of non-DB paging in the ASP the servers run in during the initial request, that is likely the problem.
For just the HTTP server, dedicating between 512 (low traffic) and 1024 MB (high traffic) usually works pretty well as a starting point. If you're using WebSphere, add 1024 MB to the starting point.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Terry Anderson
Sent: Wednesday, February 06, 2008 2:22 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Slow Page Load Using CGIDEV2.
Brad,
No matter how many people are using the application, there is only one
CGI job running:
Work with Active Jobs
Sxxxxxxx
02/06/08
13:10:43
CPU %: 4.7 Elapsed time: 00:03:53 Active jobs: 1106
Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display
message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status
CGIDEV2APA QTMHHTTP BCH .0 PGM-QZHBMAIN SIGW
CGIDEV2APA QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
CGIDEV2APA QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
CGIDEV2APA QTMHHTTP BCI .0 PGM-QZSRHTTP SIGW
CGIDEV2APA QTMHHTP1 BCI .0 PGM-QZSRCGI TIMW
I followed the advice of others and added the following line to the
config file:
StartCGI 40 QTMHHTP1.
Now the page loads within 2 - 3 seconds.
Thanks again to all who replied.
Terry Anderson
Programming Manager
Citation Corporation
Switchboard 1.251.867.5481 ext 212
Direct Line 1.251.809.2312
Fax 251.867.0525
Cell 1.251.363.4975
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx
[mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Bradley V. Stone
Sent: Wednesday, February 06, 2008 11:31 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Slow Page Load Using CGIDEV2.
I've never seen 60 seconds just for the job start either
(even on an old 170), unless it was the admin instance (that
can take at least 60 seconds even on newer faster machines)...
Try it again, but watch the CGI jobs... see if a new one
starts when you make the first request that takes 60 seconds.
Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400.
midrange.com
