@ianthetechieIan Wagner Would not know. Node once started as a non-blocking I/O multiplexing thing based on select(). Guess you mean HTTP/1.1 Persistent conns? Keep-alive is 1.0 client-driven. It all depends on request frequencies, interplay with proxies (beware of default nginx HTTP/1.0 closing after each request, I use Traefik) what would be optimal. Guess 1.1 timeouts are configurable. Eventually there are also TCP kernel conn timeout settings, that overrule as I remember...

0

If you have a fediverse account, you can quote this note from your own instance. Search https://mapstodon.space/users/justb4/statuses/114141464497201860 on your instance and quote it. (Note that quoting is not supported in Mastodon.)