Re: StartCGI bug?

I understand that the HTTP starts additional CGI server jobs up to a
configured maximum number, depending on outstanding requests. Does your web
page make multiple concurrent requests asynchronously? Our apps do.

Are you measuring milliseconds using your browser's developers tool? They
would be measuring network latency in addition to server processing. 900ms
and 160ms seem more like Java and PHP workloads. What CGI framework are you
using?



On Wed, Feb 16, 2022 at 10:06 AM Dave <[email protected]> wrote:

> Thanks Nathan,
>
> Wow and I have 2 CGI jobs to worry about, but you have to start somewhere!
>
> StartCGI is spawning the correct amount of jobs at server startup.
> When I make my first http request it lasts 900ms, subsequent requests take
> 160ms.
> After the first request, I'm getting a second pool of CGI jobs. That's what
> I don't understand. I'm imagining the 900ms is because the server is
> starting the 2nd pool of CGI jobs before it processes the request in the
> job that was pre-started.
>
>
-- 
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.