Tried that.

thanks,

75 pages is not enough for my uses.
I use 1024 pages X 4096 page size = ~ 4MB cache per process.

but the problem is that each FB Classic has to do A LOT of I/O
which slows down the entire system considerably.

FB SS has the benefit of caching often-used lookup tables in memory
between requests.

FB SS also only "locks" specific records whereas FB CS locks the
entire Database Page. This results in a lot more conflicts with CS.

-----------------

more information:
Running FB as an application with the Guardian as an application
crashes about as ofter but with a different return code:

MACHINE (Client) Fri Feb 24 09:47:32 2006
C:\Firebird\bin\fbserver.exe: terminated abnormally (3221225477)


Also It seems to NOT crash when I run FB without the guardian as
an application????

does that make any sense?

thanks,

stan

--- In firebird-support@yahoogroups.com, Daniel Rail <daniel@...> wrote:
>
> Hi,
>
> At February 23, 2006, 5:58 PM, Stan wrote:
>
> > Windows Task Manager is reporting
>
> > Mem Usage always less than 140MB
> > VM Size always less than 140 MB
>
> > I do not get the windows "out of virtual memory errors"
> > I get them when I run classic and have too many connections, but
> > not with Super Server, there is plenty of RAM and plenty of SWAP
space.
>
> What is the page cache of the database when using Classic? If it's the
> same as with Superserver, then you will encounter problems(performance
> and memory) and you should start by setting it to 75 pages(by using
> GFIX).
>
> --
> Best regards,
> Daniel Rail
> Senior Software Developer
> ACCRA Consultants Inc. (www.accra.ca)
> ACCRA Med Software Inc. (www.filopto.com)
>