On Mon, Jun 6, 2011 at 4:06 PM, heineferreira <heineferreira@...> wrote:

>
> I read in the FAQs that the classic server uses a cache for each connection. How big is this cache? Is there a default cache size and if so how usefull is it? In this forum someone posted that on 32 bit windows one must rather not use classic. I was just wondering how many connections you can have with 1gb memory. Is it ok to use classic on a 32 bit windows server if you know beforehand that you will only have a small number of users? Apparantly some queries can hog a superserver and then everyone suffers.
>

From very ancient history, Firebird descends directly from InterBase
(circa 1986) and then from Rdb/ELN, way back in the Bit Depression.
The initial performance tests were done with 10 1K buffers. The basis
of the code - now substantially rewritten - was designed for memory
sizes that would be inadequate for a modern parking meter. For
current machines you want each connection to hold the header page, the
current transaction page, a few page inventory pages, the pointer
pages for the tables you're working on, the top two levels of their
indexes, and a few data pages and index leaf pages. The more pages
you hold in cache, the more often other connections will need pages
you hold, leading to "bouncing" pages. In short, play with it a bit,
but don't be overly generous with page buffers in classic.

Good luck,

Ann