Subject | Re: AW: [firebird-support] Problem Firebird Classic Server |
---|---|
Author | Fabian Chocron |
Post date | 2008-06-10T14:38:57Z |
Hi Olaf,
In Classic each user/connection consumes (Page Size * Buffer size), so you
need to reduce it based on your max simultaneous connections and available
memory.
Let's say you have 70 users max, and 2 Gb Ram, then 2000Mb / 70 = 28 Mb
each, if pagesize is 4mb then you can have a cache of 7 pages (7 * 4 = 28).
There are other small considerations to take into account, but in principle
the above is correct.
Cheers,
Fabian
In Classic each user/connection consumes (Page Size * Buffer size), so you
need to reduce it based on your max simultaneous connections and available
memory.
Let's say you have 70 users max, and 2 Gb Ram, then 2000Mb / 70 = 28 Mb
each, if pagesize is 4mb then you can have a cache of 7 pages (7 * 4 = 28).
There are other small considerations to take into account, but in principle
the above is correct.
Cheers,
Fabian
----- Original Message -----
From: "Olaf Kluge" <olaf.kluge@...>
To: <firebird-support@yahoogroups.com>
Sent: Wednesday, June 11, 2008 12:36 AM
Subject: AW: AW: [firebird-support] Problem Firebird Classic Server
> Hello,
>
>
>
> the page size is 4096, I don't have changed it since swap to classic
> server.
> This is the same pagesize we used on superserver-architecture. How is the
> best pagesize of the classic-server? Is this the reason for the problem?
>
>
>
> We have over 60 connections to our database.
>
>
>
> Thanks for help.
>
>
>
> O. K.
>
> _____
>
> Von: firebird-support@yahoogroups.com
> [mailto:firebird-support@yahoogroups.com] Im Auftrag von Helen Borrie
> Gesendet: Dienstag, 10. Juni 2008 15:57
> An: firebird-support@yahoogroups.com
> Betreff: Re: AW: [firebird-support] Problem Firebird Classic Server
>
>
>
> At 11:07 PM 10/06/2008, you wrote:
>>Since we have cnanged our superserver to classic-Server, the Datebase size
>>of the gdb are growing. After 3 Month the database doesn't works fine and
>>hangs up on simple operations. The database has many triggers and
>>procedures. Much operations are working concurrently. Some time before, we
>>have used the Superserver without this problem.
>
> My guess is that, when you changed to Classic, you forgot to alter the
> size
> of the page cache in the database. It needs to be MUCH smaller for
> Classic,
> because the cache is not shared: every connection has its own private
> cache.
>
> So check this and report back the number of cache buffers and the page
> size.
> For the default page size of 4 Kb, the setting should be in the range
> about
> 128 to 256 pages - nowhere near the default Superserver cache size of 2048
> pages.
>
> ./heLen
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>