BIGOBJL parameter - Revision history

DmeWiccan: Automatically generated page update

2013-08-27T16:24:58Z

Automatically generated page update

← Older revision		Revision as of 16:24, 27 August 2013
Line 1:		Line 1:
			{{Template:BIGOBJL parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

JALWiccan: Automatically generated page update

2013-04-19T17:42:52Z

Automatically generated page update

← Older revision		Revision as of 17:42, 19 April 2013
Line 10:		Line 10:
	<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==

DmeWiccan: 1 revision

2012-06-22T19:25:00Z

1 revision

New page

==Summary==
<dl>
<dt>Default value
<dd>4096
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Sirius Mods</var> 7.8
</dl>
==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:
<ul>
<li>Object garbage collection
<li>End of request object cleanup
<li>File close cleanup of file objects
</ul>

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).
[[Category:System parameters]]
[[Category:Parameters]]

JAL at 01:38, 1 October 2010

2010-10-01T01:38:25Z

← Older revision		Revision as of 01:38, 1 October 2010
Line 19:		Line 19:
	These operations include:		These operations include:
	<ul>		<ul>
	<li>Object garbage collection.		<li>Object garbage collection
	<li>End of request object cleanup.		<li>End of request object cleanup
	<li>File close cleanup of file objects.		<li>File close cleanup of file objects
	</ul>		</ul>

JAL at 17:04, 30 September 2010

2010-09-30T17:04:02Z

New page

<dl>
<dt>Default value
<dd>4096
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>All
<dt>Introduced
<dd>[[Sirius Mods]] 7.8
</dl>

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:
<ul>
<li>Object garbage collection.
<li>End of request object cleanup.
<li>File close cleanup of file objects.
</ul>

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).
[[Category:System Parameters]]
[[Category:Parameters]]