Let me give you my understanding of classic vs superserver.

Superserver is multi threaded and creates one thread per connection in the same process
Classic creates one process per connection

Superserver pros - less resources
Superserver cons - cannot take advantage of multiple processors. If one connection is doing very intensive queries will impact other connections. for e.g. when a backup is running all the other clients "feel it".

Classics Server Pros - Can take advantage of multiple processors. If one connection is doing intensive querying impact on other connections is minimal
Classic Server cons - More resources. Lot of processes are created.

When to use what.

In a medium application 30 to 100 users and the hardware being used is single processor with "reasonable RAM" use superserver
In a heavy application 100+ users some of whom are making intensive use of the database but you can have multiprocessor machine with "tons of RAM" then classic server is better.

If you add embedded firebird - single user no server - you have a database which has a solution for any kind of requirement.



gk




------------------Original Message-----------

From : "plenum3" <andre@...>
To : firebird-support@yahoogroups.com
Date : 24/10/2003 1:23:37 PM
Subject : [firebird-support] Re: Superserver vs Classic Server

Just a question out of curiosity, why does the classic server still
exist?

no one should ever use anything else than superserver,
threads is just 100 times better,

I just can't understand why they did not make this obsolete as long
ago as possible.



i was just curious.



To unsubscribe from this group, send an email to:
firebird-support-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

>>>This mail is created in Hamsa. www.jlmatrix.com <<<