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



I'm not sure if concurrent requests are made asynchronously or not. All are
coming from one partner with the same external address, not our web page.
I've only noticed that, of all the other servers on our system that have
been set up by subcontractors, StartCGI 5 is indicated and there are 2
pools of 5 CGI jobs each time. Each server deals with up to 500 requests
over the course of a working day. I can see that of all the CGI jobs, only
the same 2 of 1 of the pools are ever used. When the server is started
there is 1 pool of 5 jobs, then after the first request there are 2 pools
of 5.

StartCGI is starting the correct amount of jobs at server startup. Really,
the question is, why is the first request taking so long and why do I have
twice as many jobs running afterwards as indicated in StartCGI?


On Thu, 17 Feb 2022 at 16:58, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

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 <dfx1@xxxxxxxxxxxxxx> 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: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.