Critical File Resource statistics displayed in SirMon: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (mention RKWeb equivalents)
m (<code> for menu items)
 
Line 9: Line 9:
is being viewed, but the activity that is occurring against them.
is being viewed, but the activity that is occurring against them.


In RKWeb, you can display critical file resource statistics for files or user by selecting Performance&nbsp;>&nbsp;Custom from the Monitor tab, then clicking <b>Files</b> or <b>Users</b> along with the <b>Critical File Resource</b> drop-down menu item.  
In [[RKWeb]], you can display critical file resource statistics for files or user by selecting <code>Performance&nbsp;>&nbsp;Custom</code> from the <code>Monitor</code> tab, then clicking <b>Files</b> or <b>Users</b> along with the <b>Critical File Resource</b> drop-down menu item.  


<table class="thJustBold">
<table class="thJustBold">

Latest revision as of 20:02, 6 June 2017

Critical File Resource statistics describe activity which is occurring against the four critical file resources: DIRECT, INDEX, EXISTS, and RECENQ. Each of the critical file resources protects the integrity of a Model 204 file structure.

Critical file resource statistics are provided by SirMon to assist in diagnosing second order performance problems. Keep in mind that the resources themselves are not what is being viewed, but the activity that is occurring against them.

In RKWeb, you can display critical file resource statistics for files or user by selecting Performance > Custom from the Monitor tab, then clicking Files or Users along with the Critical File Resource drop-down menu item.

BUFPAGE Total number of pages in the disk buffer pool currently occupied by pages from all tables in the database file. Equal to BUFPAGA+BUFPAGB+BUFPAGC+BUFPAGD+BUFPAGF.
CFRCDIR Conflicts on the DIRECT critical file resource (rate or total). This resource protects the integrity of Table B.
CFRCEXS Conflicts on the EXISTS critical file resource. This resource protects the integrity of the existence bit map.
CFRCIND Conflicts on the INDEX critical file resource. This resource protects the integrity of the database indexes.
CFRCREC Conflicts on the RECENQ critical file resource. This resource protects the integrity of the record enqueueing tables.
CFRQDIR Number of users waiting for the DIRECT critical file resource. This resource protects the integrity of table B.
CFRQEXS Number of users waiting for the EXISTS critical file resource. This resource protects the integrity of the existence bit map.
CFRQIND Number of users waiting for the INDEX critical file resource. This resource protects the integrity of the database indexes.
CFRQREC Number of users waiting for the RECENQ critical file resource. This resource protects the integrity of the record enqueuing tables.
CFRQUEU Number of users waiting for any critical file resource.
DKRD Physical page reads from a Model204 database file or CCATEMP.
DKWR Physical page writes to a Model 204 database file or CCATEMP.
HDDIRCT Type of enqueue on the critical file resource that protects the Table B records (EXC, SHR, or blank).
HDEXIST Type of enqueue on the critical file resource that protects the existence bit map (EXC, SHR, or blank).
HDINDEX Type of enqueue on the critical file resource that protects the Table C and D indexes (EXC, SHR, or blank).
HDRECNQ Type of enqueue on the critical file resource that protects existence bit map pages for locked record sets (EXC, SHR, or blank).
PNAME Name of the currently executing or last executed procedure.

See also