How does the CGI app get its' data? Traditional SETLL/READE or SQL? SQL might be reusing a index that gets build on the first call or it could just be that the system has all the data in RAM on the second call and makes the process faster. I have some batch jobs which I run that might take 2-3 minutes on the first run and only 1 on any subsequent runs done shortly after. I have always attributed this to the data being in RAM. It is also that the problem is on the client end. The first call will need to launch the browser and all of its dll's (if your windows) the second one will be faster if windows has all that loaded. You could try an experiment from two different PCs. Have one run the CGI app and then a few seconds later have the second do the same. If the first time speed is the same for both it would make me think it's a client side issue. If the first is slow and the second fast it is a server side issue
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Richard ECUYER
Sent: Wednesday, February 06, 2008 11:53 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Slow Page Load Using CGIDEV2.
the only time i a saw a difference like that between first load an
others, was when the first one had to start the cgijob.
Terry Anderson a écrit :
OK, here is what's happening.
The user takes an option from a green screen menu that launches a web page. The first time the user takes the option, the page takes about 60 seconds to load. After that, the page loads in 2 - 3 seconds. Has anyone seen anything like this before?
I am using the apache server on a 525 at V5R4.
Switchboard 1.251.867.5481 ext 212
Direct Line 1.251.809.2312
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,
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.