>> Run gstat -h and report back.
>>
>>
>> --
>> With regards,
>>
>> Thomas Steinmaurer
>
>
> Hello Thomas, Page buffers is 0, the database has a lot of metadata, more than 1000 tables 3000 triggers and 1500 stored procedures.

Ah, ok. I guess, this makes a difference, because metadata cache
possibly plays an important role here then.

> If classic server uses 100 MB per client connection, then classic is not for me, but i don't know how to improve performance for 100 or more users.

Is it really 100MB per client connection?

> Database header page information:
> Flags 0
> Checksum 12345
> Generation 16764
> Page size 8192
> ODS version 11.2
> Oldest transaction 3220
> Oldest active 16672
> Oldest snapshot 16672
> Next transaction 16752
> Bumped transaction 1
> Sequence number 0
> Next attachment ID 96
> Implementation ID 16
> Shadow count 0
> Page buffers 0
> Next header page 0
> Database dialect 1
> Creation date Apr 28, 2011 11:10:03
> Attributes force write
>
> Variable header data:
> Sweep interval: 20000
> *END*

So, page buffers is the default one as configured in firebird.conf. If
not configured, it is 75 for classic.

Two things here:

- I'm not sure if it is important RAM-wise, but your oldest interesting
transaction got stuck. Try to run a sweep.

- You could pump down the data page cache per client connection by
decreasing the database page size from 8K to 4K, thus you end up with a
smaller data page cache.

But, all in all. Today you get more RAM nearly for "free" (e.g. here in
Austria, a 8GB desktop RAM kit (2x4GB) costs about 60 EUR). So, I simply
would install more RAM. Period.



--
With regards,

Thomas Steinmaurer
Upscene Productions
http://www.upscene.com
http://blog.upscene.com/thomas/

Download LogManager Series, FB TraceManager today!
Continuous Database Monitoring Solutions supporting
Firebird, InterBase, Advantage Database, MS SQL Server
and NexusDB!