Subject | Re: Firebird 2.5 SuperClassic on Linux 64 -OS memory allocation problem |
---|---|
Author | Kris B |
Post date | 2011-02-17T10:31:51Z |
Hi,
Build im using is FirebirdCS-2.5.0.26074-.amd64
In my firebird.conf DefaultDbCachePages was hashed out so I assumed this would default to 75 as it was a SuperClassic install?
Also as the Page Buffer was set in DB1 at 2048 I thought that would override any setting in the conf file. Loooking at the FB log this seems to be confirmed as I see a few "Allocated 78 page buffers of 2048 requested" messages for DB1 only.
Ive unhashed DefaultDbCachePages and set it to 75, as well as setting DB1s page buffer to 0 using GFix.
On my server with 10 users connecting to my 3dbs what sort of value for DefaultDbCachePages would you usually recommend for Classic/SuperClassic? Even when FB is saying it cant allocate memory from OS the service is only using 5% of available RAM and /tmp is about 10% full.
Thanks for your help!
Cheers,
Kris
Build im using is FirebirdCS-2.5.0.26074-.amd64
In my firebird.conf DefaultDbCachePages was hashed out so I assumed this would default to 75 as it was a SuperClassic install?
Also as the Page Buffer was set in DB1 at 2048 I thought that would override any setting in the conf file. Loooking at the FB log this seems to be confirmed as I see a few "Allocated 78 page buffers of 2048 requested" messages for DB1 only.
Ive unhashed DefaultDbCachePages and set it to 75, as well as setting DB1s page buffer to 0 using GFix.
On my server with 10 users connecting to my 3dbs what sort of value for DefaultDbCachePages would you usually recommend for Classic/SuperClassic? Even when FB is saying it cant allocate memory from OS the service is only using 5% of available RAM and /tmp is about 10% full.
Thanks for your help!
Cheers,
Kris
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> At 11:54 AM 17/02/2011, Kris B wrote:
> >Looking at DB1 the Page Buffer is 2048? Not sure why -that is the Super Server default setting. I'll set this to zero and test
>
> As you left DefaultDbCachePages at 2048, it won't make any difference.
>
> You haven't mentioned which build you installed but 2048 *is* way too high for Classic/Superclassic 32-bit, even if you are running it on the 64-bit OS. Knock DefaultDbCachePages down to 75 pages and don't forget to erase the '#' character! Also remember that it won't kick in until everyone is off and someone reconnects.
>
> You can ease it up a bit later if it seems that the combined total of RAM for the three databases is well short of 2 GB at peak.
>
> ./heLen
>