Subject | Re: firebird classic on windowx 2000|xp|2003 |
---|---|
Author | Adam |
Post date | 2008-01-24T10:35:11Z |
--- In firebird-support@yahoogroups.com, "mohamed.banaouas"
<mohamed.banaouas@...> wrote:
which all connections can use, whereas the cache in Classic is per
connection (and hence the cache is usually smaller). It is cheaper to
establish a new thread than a new process, so another win for
Superserver. But Superserver can not make use of SMP. It is bound to a
single CPU core, whereas classic can. This is a big win for classic.
If there was an architecture that performed better under all
situations, I highly doubt both of them would be maintained.
Adam
<mohamed.banaouas@...> wrote:
>It is just different to Superserver. Superserver has a shared cache
> hi all,
> Does any one tested firebird classic on windows plateform ?
> I mean, is it faster than superserver, even if it requires moore ram?
which all connections can use, whereas the cache in Classic is per
connection (and hence the cache is usually smaller). It is cheaper to
establish a new thread than a new process, so another win for
Superserver. But Superserver can not make use of SMP. It is bound to a
single CPU core, whereas classic can. This is a big win for classic.
If there was an architecture that performed better under all
situations, I highly doubt both of them would be maintained.
Adam