On 12/22/05, goran@krampe.se goran@krampe.se wrote:
Now - the system in question will possibly involve around 100 concurrent users. And most of them will be readers. So.... :) any ideas on "smarter" solutions to that issue?
Kiluaea does connection pooling for Magma. You'll only need as many sessions as you'll have maximum concurrent transactions (compared to concurrent sessions, this can easily make one or two orders of magnitude difference).