Subject Connection resources, classic vs. SS
Author Jason Wharton
I am aware that memory allocated to a server process is directly
proportional to the page size and number of connections to a database. In
the classic architecture this makes sense as each connection ends up being
serviced by a separate process. This also explains why this architecture
doesn't feasibly scale to more than 256 concurrent users.

But, in the super-server architecture, connections are actually serviced by
a single process such that allocated resources are shared in common rather
than separated across process boundaries. What I am wondering is if the
resource allocation parameters are still the same or if there is a
difference such that new connections will cap out and not add additional
resource allocations.

What I am driving at is: With going to SS is it possible that resource
allocations can become more independent from the number of concurrent
connections such that the number of connections can significantly increase?
What is the next point of exhaustion that would limit the number of
concurrent connections?

I can see how the battle between classic and SS is going to get potentially
sore as each will need to grow in ways that widens the divide in order that
the strengths of each are more fully realized.

Jason Wharton
CPS - Mesa AZ