> That said, many of these things are solvable without a full switch to a threaded model (eg. by having pooling built-in and session-state-aware). The thing is

> That said, many of these things are solvable without a full switch to a threaded model (eg. by having pooling built-in and session-state-aware). The thing is that that's a lot easier with threads. Much of the session state lives in process private memory (prepared statements etc), and it can't be statically sized ahead of time. If you move all that state into dynamically allocated shared memory, you've basically paid all the price for threading already, except you can't use any tooling for threads.