BIGOBJL parameter: Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
(Automatically generated page update) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Template:BIGOBJL parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 10: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Sirius Mods</var> 7.8 | <dd><var class="product">[[Sirius Mods]]</var> 7.8 | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
Latest revision as of 16:24, 27 August 2013
Size of object list considered big
Summary
- Default value
- 4096
- Parameter type
- System
- Where set
- System manager resettable
- Related products
- All
- Introduced
- Sirius Mods 7.8
Description
This parameter indicates the minimum size of the internal object list in CCATEMP that is considered "big." If the number of items on the object list is greater than or equal to BIGOBJL, certain CPU-intensive operations are forced to parallel mode in an MP/204 Online so that they are eligible to run in an MP subtask. These operations include:
- Object garbage collection
- End of request object cleanup
- File close cleanup of file objects
Setting BIGOBJL in a non-MP/204 Online will have no effect. Setting BIGOBJL to a negative value will prevent the indicated operations from being forced to run in parallel, though some of them might run in parallel, anyway (because they were invoked in parallel mode).