On 27/12/2017 10:08, Andres Freund wrote:
Optimizing for this seems like a pointless exercise. If the goal is efficient
processing of 100k connections the solution is a session / connection
abstraction and a scheduler. Optimizing for this amount of concurrency just
will add complexity and slowdowns for a workload that nobody will run.
Isn't that what's suggested?
The difference is that the session scheduler is inside the server.
Accepting 100k connections is no problem these days - giving each of
them an active thread seems to be the issue.
