05.07.2011 21:29, Paul Reeves wrote:
>> FW and HDD settings don't affect the page I/O stats.
>
> Actually, FW must affect the I/O stats
Sorry, but it doesn't not. Our I/O stats reports page writes performed
by the engine (OS call). They could either reach the disk (FW=ON) or
stay in the file sy
05.07.2011 21:32, Paul Reeves wrote:
>> Are you running SuperServer, Classic or SuperClassic?
>
> It is super server, although this should not make any difference.
Classic doesn't have any background I/O activity, so there will be a
difference.
Dmitry
-
On Wednesday 6 July 2011 at 09:06 Dmitry Yemanov wrote:
>
> Sorry, but it doesn't not. Our I/O stats reports page writes performed
> by the engine (OS call). They could either reach the disk (FW=ON) or
> stay in the file system cache (FW=OFF), but the write has happened and
> it's reflected in th
Dmitry
> > Ah, that is interesting. I don't think that is documented. I was under
> > the impression that stat_group 0 was cumulative for all connections
> > since the start of the server.
>
> Stats don't exist without active connections, as there are no resources kept
> inside the engine in the
Sean,
> How are the IO related to the background/cooperative garbage collection
> function accounted for?
>
> Is it the case that if my connection encountered old versions, that the IO
> from the background cleanup of those items is counted against my connection?
Cooperative GC is accounted in
Aliases for returning
-
Key: CORE-3546
URL: http://tracker.firebirdsql.org/browse/CORE-3546
Project: Firebird Core
Issue Type: New Feature
Reporter: Alexander Chiryatjev
Priority: Minor
It's seem
