Subject Connections vs. Transactions
Author Dan Palley
In the current Super Server architecture, for a large number of connections,
why is connection pooling more efficient than having one (or more)
persistent connections per user?

Seems to me that one connection with 10 active transactions would put the
same load on the server as 10 connections each with one active transaction.

Are connections a resource issue at the OS level, and, therefore, beyond the
control of Interbase? I would think that each connection spawns a thread,
but aren't threads relatively lightweight?

I guess what I'm asking is: If the OS supports thousands of threads, can IB
support thousands of connections or is there some internal mechanism in IB
that bogs down after a certain number of connections.