MAXUD parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:MAXUD parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
Line 10: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V3.2.0</var> or earlier | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The number of milliseconds beyond which a user's update unit is counted as a long update unit</p> | <p>The number of milliseconds beyond which a user's update unit is counted as a long update unit</p> |
Latest revision as of 13:51, 4 August 2015
Long update unit durations (ms)
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On User 0's parameter line; not resettable
- Related products
- All
- Introduced
- Model 204 V3.2.0 or earlier
Description
The number of milliseconds beyond which a user's update unit is counted as a long update unit
The number of long update units and the total duration in milliseconds of all long update units are kept per user for user, since-last, and system statistics. Long update units are not tracked per file.
The update unit is considered to have started at the time of update of the first, local, non-HLI file, and to end at commit or backout.
Both backoutable update units and non-backoutable update units can become long update units.
If MAXUD=0, Model 204 does not recognize long updates.