Subject | Re: [firebird-support] superserver & classic server |
---|---|
Author | Fabian Chocron |
Post date | 2004-02-24T10:22:35Z |
> Hi all,I can comment on the difference over Windows.
> I would like to know what's the difference between a firebird
> superserver and classic server.
Superserver on Windows: 1 applicacion for all the connected clients. So the
application uses "internal threading". Because of that, the database cache
memory is only 1 for all the users. It can not take more than 1 processor
(CPU) because it goes crazy and works slower than a single processor
machine.
Classic Server on Windows: 1 applicacion as a coordinator, plus 1
applicacion per user (the coordinator starts and kills the apps as the users
connects and disconnects). Because there are different apps (.exes) the
memory is not shared, so it allocates much more ram. On the other hand, it
is faster because windows manages the different apps (.exes) much better
than the internal threading. You can use a multiprocessor machine.
Conclusion: unless you need "real time response" it is more logical to use
SuperServer. If you need super fast response, classic server will deliver
better performance, but you need to configure a "Strong Server" with
multiple processors and lots of RAM.
Cheers
Fabian.
PS: all this info is from experience, not "theory".