On 5.2.2025 19.46, Greg Haverkamp via radiator wrote:
> What we've witnessed is that, over time, the http connections become
"stale", for lack of a better term. They start preventing any outbound
traffic, almost as if they're not recycled. I can eliminate some of
this by going to 1 Connection, and it wasn't until today that I realized
we could go to 0.
The parameters that set timeouts, number of connections, etc. are
available are listed here:
https://files.radiatorsoftware.com/radiator/ref/HTTPClient_common_httpclient.html#HTTP
Have you, for example, set NoreplyTimeout to a non-default value?
It sounds like a "stale" connection is still waiting for something or is
not correctly put back to the pool of available connections. Do you see
any log messages that might relate to this?
But mostly I'm wondering if others have seen this, if there are system
settings that accommodate this better, etc.
I'd say the parameters common to HTTP clients, link above, are the ones
to experiment with first. However, if you could let us know how the
parameters are set now, I could see if I can reproduce the problem. How
slow is your "slowish" backend? Is it sometimes faster or very slow or
simply constantly slow?
Thanks,
Heikki
--
Heikki Vatiainen
Radiator Software, makers of Radiator
Visit radiatorsoftware.com for Radiator AAA server software
_______________________________________________
radiator mailing list
[email protected]
https://lists.open.com.au/mailman/listinfo/radiator
