There is not only RAM limits, but also system resources available. How
many file handles, threads etc. can a Windows Server create/use ?
I know that under Linux, these limits exists and you need to tweak the
kernel ("too many open files" before using only a 10% of the available RAM).
I've never tested FB2.5SC under Windows, but we did encounter the same
kind of problem using classic server under windows and switched to Linux
(also for other reasons).

Greg

Le 26/10/2010 13:52, tomkrej a écrit :

>
> Yes we have move it from IB7.5 superserver (2CPU support)
>
> But we calculated it for classic server
>
> 16kB page * 8192 pages * 40 users = 5120 MB
> 16MB temp * 40 users = 640 MB
>
> together 5.625GB of 8GB fyzical ram.
>
> Is there a limit on Win2003 32bit of available RAM??
> If Yes, would be the Classic Server solution for this?
>
> We'll try both - the lower cache and temp - and - classic server
>
> Thank You, Tom
>
> --- In firebird-support@yahoogroups.com
> <mailto:firebird-support%40yahoogroups.com>, Menetrier Gregory
> <gregory.menetrier@...> wrote:
> >
> > Hi Tom,
> >
> > Not sure, but are you migrating from a SuperServer to a SuperClassic ?
> > If yes, i felt on the same problem.
> > You're getting out of system resources.
> > You should lower the number of PageBuffers allocated for each
> connection
> > (in SuperServer, the cache is shared not in SC).
> > It should be between 128 to 512 PageBuffers according to your
> > OS/Resources/Nb of client.
> >
> > Greg.
>
>

[Non-text portions of this message have been removed]