Subject | Re: [firebird-support] Re: DB-Inserts slow after 5000 inserts (with select) |
---|---|
Author | Ann Harrison |
Post date | 2011-06-15T18:30:03Z |
On Wed, Jun 15, 2011 at 1:00 PM, Jens Saathoff <jensesaat@...> wrote:
two weeks. Basically, it depends on which Firebird architecture
(classic, superserver, superclassic, or embedded) you're using and
whether your environment is 32 or 64 bit. The "page buffer" parameter
determines how much memory Firebird uses to cache database pages and
reduce I/O. For SuperServer, the amount of memory in bytes is the
page buffer value times the page size. The others allocate that
amount for each client, so if you have 200 active clients on classic,
a page buffer value of 400, and a 4096 byte page size, you're using
about 163Mb of memory to hold database pages.
Until you get other problems - like defining the indexes you need -
under control, just go with the default page buffers.
I didn't understand your comment about the slowness of gen_id.
Good luck,
Ann
>There was a long discussion on that subject recently - within the past
> What can i do with "page buffer"? What it's useful for? Which value is the
> best? What does it do?
>
two weeks. Basically, it depends on which Firebird architecture
(classic, superserver, superclassic, or embedded) you're using and
whether your environment is 32 or 64 bit. The "page buffer" parameter
determines how much memory Firebird uses to cache database pages and
reduce I/O. For SuperServer, the amount of memory in bytes is the
page buffer value times the page size. The others allocate that
amount for each client, so if you have 200 active clients on classic,
a page buffer value of 400, and a 4096 byte page size, you're using
about 163Mb of memory to hold database pages.
Until you get other problems - like defining the indexes you need -
under control, just go with the default page buffers.
I didn't understand your comment about the slowness of gen_id.
Good luck,
Ann