SQLLPLIM parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:SQLLPLIM 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.1</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The limit on the number of significant internal operations that a user can execute without swapping (giving up the processor to another user)</p> | <p>The limit on the number of significant internal operations that a user can execute without swapping (giving up the processor to another user)</p> | ||
Latest revision as of 15:29, 7 September 2017
SQL read/writes per slice
Summary
- Default value
- 200
- Parameter type
- User
- Where set
- On user's parameter line (CCAIN); can be reset by any user
- Related products
- All
- Introduced
- Model 204 V3.1
Description
The limit on the number of significant internal operations that a user can execute without swapping (giving up the processor to another user)
SQLLPLIM swaps a query when it reaches SQLLPLIM internal operations, which includes indexed finds, fetching from files and intermediate result tables, and writing to files and intermediate result tables. The SQLLPLIM counter returns to zero when the query regains control of the processor.
SQLLPLIM is an integer value whose minimum is 0, maximum is 32767, and default is 200. Setting SQLLPLIM too low can cause excessive swapping for users in a busy Online.