Subject Re: Running out of database!
Author Stan
you have to give a lot more information.

7 * 30 = 210 concurrent connections. Depending on the
load (what these connections are doing) and on DB server specs,
this might be pretty good performance. Or not. it all depends:

DB Server specs?
All connections are busy?
what kind of queries?
what happens when the DB server "cant keep up"?
etc, etc, etc.

--- In, "hay77772000" <dhay@...> wrote:
> Hi,
> We have a series of severs that are each running Tomcat, and load
> balanced through Apache. They all share the same firebird database on
> a dedicated machine on the backend - v1.5. We initially started with
> SuperServer, but had stability and other problems with that, so we
> switched to Classic. Each server uses a db connection pool with
> approx 30 connections.
> When we scale up, we seem to hit a wall at around 7 servers, where the
> database machine cannot keep up.
> Can anyone suggest ways that we can get around this issue? Does
> anyone have experience with some of the other "commercial" dbs -
> Oracle/Sql Server etc.? Would switching to one of these likely help us?
> many thanks,
> David