CFRWPCT parameter: Difference between revisions
m (link repair) |
|||
| Line 13: | Line 13: | ||
<dd><var class="product">Model 204 V6.1</var> or earlier | <dd><var class="product">Model 204 V6.1</var> or earlier | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>Specifies the percentage of servers | <p> | ||
<p>When you issue a < | Specifies the percentage of servers (<var>[[NSERVS parameter|NSERVS]]</var>) that can be occupied by non-swappable users waiting for exclusive access to a critical file resource (CFR). These file-level resources consist of DIRECT, EXISTS, INDEX, and RECENQ.</p> | ||
<p> | |||
When you issue a <code>[[VIEW command|VIEW CFRWPCT]]</code> command, the value returned is the actual number of servers (<code>CFRWPCT * NSERVS</code>), not the percentage of, that might contain users in a non-swappable wait for CFR in EXCL mode.</p> | |||
====Performance tuning access to critical file resources==== | ====Performance tuning access to critical file resources==== | ||
<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p> | <p> | ||
<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p> | The <var>CFRWPCT</var> parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p> | ||
<p> | |||
When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, <var>CFRWPCT</var> can be set to allow up to 75 percent of <var>NSERVS</var> to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p> | |||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 20:30, 20 May 2015
Max nonswappable CFR waiters
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- Set in CCAIN, not resettable, range 0-75 percent
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
Specifies the percentage of servers (NSERVS) that can be occupied by non-swappable users waiting for exclusive access to a critical file resource (CFR). These file-level resources consist of DIRECT, EXISTS, INDEX, and RECENQ.
When you issue a VIEW CFRWPCT command, the value returned is the actual number of servers (CFRWPCT * NSERVS), not the percentage of, that might contain users in a non-swappable wait for CFR in EXCL mode.
Performance tuning access to critical file resources
The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access.
When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.