Subject Re: [firebird-support] re: switching over to Classic server
Author Thomas Steinmaurer

> We are running Firebird SuperServer on an installation that has
> approx. 500 connections (sometimes more). We are hitting the 3GB
> process limitation on 32-bit Windows which takes the fbserver service
> down almost daily. Performance has not been an issue other than the
> aforementioned problem - we are considering switching over to
> Classic. Is there anything that we should be worried about? We
> realize we may take a bit of a performance hit for initial
> connections, but if it keeps the server from crashing....
> We have been working on connection pooling, but have found that
> performance is not to our liking. We are also in initial testing of
> our product with Firebird 2.1. Of course, going to 64-bit would get
> us around the limitation altogether. Any suggestions or help would
> sincerely be appreciated. Thanks.

As Adam has mentioned, perhaps you have chosen a to optimistic page
buffers setting which will let you run out of memory on a server which
hosts several Firebird databases.

Classic is more ressource (RAM) intensive, because each client
connection holds its own cache specified by the database page buffers

There is one nice migration trap when switching from Super to Classic
when using events. The remote aux port settting for specifying a
particular port for event processing is a super server setting only. At
least it was in 1.5 and I don't think it has been changed in 2.0. But I
could be wrong here. Just in case you are using events in a firewalled

Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions