Subject | Re: [firebird-support] Generator Performance |
---|---|
Author | Matheus Degiovani |
Post date | 2011-09-26T13:43:58Z |
Hello Ann,
page, right?
So, if I had a large number of generators, for workloads which accessed
generators on different pages (say, generator ID 10 and generator ID 4000)
there wouldn't be contention, right?
Is there a way of finding out how many pages are used to store a given
table? Or documentation about how the mapping from tables to memory and
disk pages are implemented on firebird?
Anyway, thanks for the info!
Cya.
--
Matheus Degiovani
Gigatron Software e Treinamentos Ltda.
(18) 3649-4045
MSN: matheus@...
--
CrĂticas ou Sugestões? Ligue para Ouvidoria Gigatron: (18) 3649-4048
>This "page" is the mapping of a set of table records into a memory/disk
> Generator values are stored on generator pages. In shared cache
> architectures (i.e. SuperServer) a connection that changes a generator
> value
> gets a transient write lock on the page, makes its change and releases
> the
> page.
page, right?
So, if I had a large number of generators, for workloads which accessed
generators on different pages (say, generator ID 10 and generator ID 4000)
there wouldn't be contention, right?
Is there a way of finding out how many pages are used to store a given
table? Or documentation about how the mapping from tables to memory and
disk pages are implemented on firebird?
Anyway, thanks for the info!
Cya.
--
Matheus Degiovani
Gigatron Software e Treinamentos Ltda.
(18) 3649-4045
MSN: matheus@...
--
CrĂticas ou Sugestões? Ligue para Ouvidoria Gigatron: (18) 3649-4048