Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Client runtimes experience slow response times during heavy loads (perhaps sometimes even exhausting the DEFAULT-TIMEOUT value and returning “9D,05”). Is there anything I can do?

0
Posted

Client runtimes experience slow response times during heavy loads (perhaps sometimes even exhausting the DEFAULT-TIMEOUT value and returning “9D,05”). Is there anything I can do?

0

Here are several options to consider: 1) AcuServer is single-threaded, handling a single request from a single client runtime to completion before attending to requests from other client runtimes, which are queued up in a manner dependent on the server’s operating system. Slow response time may indicate that a single copy of AcuServer cannot keep ahead of the queued requests at times of peak load. If the load on AcuServer is variable, the DEFAULT-TIMEOUT tolerance allowed by client runtimes may be sufficient most of the time, but may be too brief to allow for the times when AcuServer is heavily burdened. In those cases, setting DEFAULT-TIMEOUT to a higher value can avoid the timeout errors. (On the other hand, if AcuServer is actually unable to access the data for some other reason-such as insufficient file permissions-then increasing DEFAULT-TIMEOUT only increases the amount of time that transpires before the client runtime returns the error message.) If there are sufficient system re

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123