Subject | AW: AW: [firebird-support] Problem Firebird Classic Server |
---|---|
Author | Olaf Kluge |
Post date | 2008-06-10T14:36:29Z |
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:
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]
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 sizeMy guess is that, when you changed to Classic, you forgot to alter the 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.
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]