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



15 seconds from log on to the first page sounds extraordinarily slow to me - but you described it as normal? Do you really expect it to be that slow - what is going on at that point?

If a thread disconnects following inactivity (in your case 5 minutes) then when it starts a new thread when a request finally arrives then there will be a small overhead while that happens - but again 30 seconds is terrible. It should be negligible from a user perspective. In any case unless you are running persistent CGI (a bad idea in my opinion) then even if a user twiddled their thumbs for more than 5 minutes a thread should still be kept busy by requests from other users.

There seems to be something fundamentally wrong with the performance of the server despite the default settings - or your application. Does the latter do some sort of long winded initialisation?


Sent from my iPad


[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
On 10 Aug 2017, at 17:23, Hohlen, Kent <Kent.Hohlen@xxxxxxxxxxxxxxx> wrote:

[External Email]
________________________________



Buck - Thanks for your help and suggestions. I wasn't able to get the logging to work.

While looking through the server's properties, I came across a setting that corresponds to the latency issues we are seeing. Under System Resources there is "Time to wait between requests:". The help for this value sounds like it keeps the connection alive for this value. This value defaulted to 5 minutes, which was exactly the time I noticed in my testing. If I change this value to something greater than 5 minutes, the latency corresponds to this value. Is there any harm to setting this value to something like 4 hours? I'm also thinking of changing the value of "Maximum requests per connection:" to unlimited. This server only services our intranet, so I can't see any harm in changing either value. Testing this change in our test environment didn't show any issues.

Thanks,
Kent

--
This is the Web Enabling the IBM i (AS/400 and 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.




________________________________
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.