Hi Nigel

We choose to use the Super Server version of FB based on the following
information at

http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_ss_vs_classic


"The Classic implementation predates the SuperServer implementation, and
the SuperServer implementation is the future of InterBase.

Classic configuration is used on operating systems that currently don't
have the technology for threaded applications, which is required for
SuperServer. InterBase also distributes the Classic version on platforms
that have threading technology, but which benefit from the low-profile
implementation.

SuperServer has a greater ability to meet the demands of a growing
multi-user system, while retaining good performance and efficiency.
SuperServer is implemented in InterBase product on all platforms where
it is technically practical. It is the intention that SuperServer is the
future direction of InterBase on all platforms. "

SMPServer and Slimserver would only be appropriate in the short term.
Long term I would expect SuperServer to be the way to go.

Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd



Nigel Weeks wrote:

>The reason here is that you're using SuperServer on machines with multiple
>cpu's - regardless of whether they're Logical or Physical.
>
>If you've got multiple CPU cores, use Classic. It's the only one that
>scales, and it means your application won't block all other requests while
>it's doing a large query.
>
>Most likely the above is an over-simplistic answer, but all I've ever used
>over the last four years is classic, and no query/export/report has ever
>blocked other people from working...
>
>Nige.
>
>ps. We could consider renaming the versions of Firebird:
>Embedded -> Embedded
>SuperServer -> SlimServer (Single processor)
>Classic -> SMPServer (Multiple Processor)
>
>
>
>
>
>
>