> We have a machine running Win XP with 3GB Ram. It has a 1.5GB DB with
> 8192kb pages and buffers set to 20000 (was a super server DB). It has
> been running FB 2.1.3 SuperServer however performance has been
> terrible. This morning I changed it to 2.5 super classic. With only a
> few connections (less then 5) DB connection time slows to a crawl and
> the FB log shows...
>
>
> CHREOS01 Tue Nov 09 09:05:41 2010
> Database: C:\CHREOS\TRANSFERSYS\SOAPEDI.FDB
> Allocated 572 page buffers of 20000 requested
>
>
> CHREOS01 Tue Nov 09 09:05:42 2010
> unable to allocate memory from operating system
>
>
> CHREOS01 Tue Nov 09 09:05:42 2010
> Database: C:\CHREOS\TRANSFERSYS\SOAPEDI.FDB
> Allocated 572 page buffers of 20000 requested
>
>
> This seems to indicate a RAM / resources issue however the machine shows
> it using about 1.2GB of 3GB. I know I should reduce the buffer size for
> this DB however I dont want to rebuild it to FB 2.5 ODS yet as I may
> need to move it to another 2.1.3 machine. Any suggestions?

Yes. Vastly decrease the page buffers value, because SuperClassic uses a
separate cache per connection as in ClassicServer. Check out my V2.5
architecture comparison sheet on my blog:
http://blog.upscene.com/thomas/index.php?entry=entry091016-133211


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/