Subject | Re: [firebird-support] Index Caching |
---|---|
Author | Ann W. Harrison |
Post date | 2007-02-17T17:40:06Z |
leugim@... wrote:
fetch vs. read, mark vs. write. Each fetch is a request for
a page that is satisfied in cache. Each read is a request for
a page that is not in cache. A mark is a change to a page in
cache, a write moves the page back to disk. There are debugging
statements in the code that might let you trace the actual
flow of page in the cache, but they haven't been used in many
years and would certainly have a terrible effect on performance.
Regards,
Ann
> Hello!Not really. You can look at the ratios in performance statistics
> Is it possible to see what is in a cache? Some kind of stats to see how
> the cache is working? Memory map? etc.
> Regards,
> ...michal
fetch vs. read, mark vs. write. Each fetch is a request for
a page that is satisfied in cache. Each read is a request for
a page that is not in cache. A mark is a change to a page in
cache, a write moves the page back to disk. There are debugging
statements in the code that might let you trace the actual
flow of page in the cache, but they haven't been used in many
years and would certainly have a terrible effect on performance.
Regards,
Ann