05.07.2011 10:23, Paul Reeves wrote:
>
> All tests are run from a freshly restored backup containing 100,000 rows in
> the test table. Forced Writes are ON and hard drive disc caches are disabled.
> Firebird 2.1.4 is the server.
FW and HDD settings don't affect the page I/O stats.
> The attachmen
Paul,
I don't know about the engine stats tracking but...
> Does anyone know why these inconsistencies exist?
Are you running SuperServer, Classic or SuperClassic?
Have you considered the effect of garbage collection?
Have you considered the cost of indirect (ie. indexes) pages which could be
On Tuesday 5 July 2011 at 17:27 Dmitry Yemanov wrote:
>
> FW and HDD settings don't affect the page I/O stats.
Actually, FW must affect the I/O stats - see my first post in this thread for
an example. The only difference between those figures and the second set are
that the FW was off in the f
On Tuesday 5 July 2011 at 18:40 Leyne, Sean wrote:
>
> Are you running SuperServer, Classic or SuperClassic?
It is super server, although this should not make any difference. The code
that collects the stats is at a very low level. It is related to when the O/S
system calls are made to physica
Paul,
> > Are you running SuperServer, Classic or SuperClassic?
>
> It is super server, although this should not make any difference. The code
> that collects the stats is at a very low level. It is related to when the O/S
> system calls are made to physically read/write to disc.
With cooperativ
On Tuesday 5 July 2011 at 19:44 Leyne, Sean wrote:
>
> With cooperative garbage collection, it is not the active request which
> performs the garbage collection, but a background one.
>
The database is freshly restored. There is no garbage. The test executes one
statement and commits.
GC can
