MAXDAEM parameter - Revision history

JAL: move RKTools note

2017-11-22T16:57:16Z

move RKTools note

← Older revision		Revision as of 16:57, 22 November 2017
Line 3:		Line 3:
	<dl>		<dl>
	<dt>Default value		<dt>Default value
	<dd>1		<dd>1
	<dt>Parameter type		<dt>Parameter type
	<dd>System		<dd>System
Line 9:		Line 9:
	<dd>User 0 CCAIN parameters		<dd>User 0 CCAIN parameters
	<dt>Related products		<dt>Related products
	<dd>All.		<dd>All
	~~<p><b>NOTE:</b> If using any of the RKTools such as SIRMON, SIRSCAN, SIRPRO etc., the minimum required is MAXDAEM=10.</p>~~
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">[[Sirius Mods]]</var> Version 6.7		<dd><var class="product">[[Sirius Mods]]</var> Version 6.7
Line 16:		Line 15:

	==Description==		==Description==
	This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by <var>[[New (~~Daemon_constructor~~)\|New]]</var> method for <var>[[Daemon class\|Daemon]]</var> objects; or by a number of the (deprecated) ~~Sirius~~ [[List of $functions\|$functions]] such as: <var>[[$CommBg]]</var>, <var>[[$Command]]</var> or <var>[[$CommndL]]</var>.		This parameter indicates the maximum number of [[Sdaemons\|sdaemon]] threads that can be used by an individual thread. Such threads are allocated by <var>[[New (Daemon constructor)\|New]]</var> method for <var>[[Daemon class\|Daemon]]</var> objects; or by a number of the (deprecated) [[List of $functions\|$functions]] such as: <var>[[$CommBg]]</var>, <var>[[$Command]]</var> or <var>[[$CommndL]]</var>.

	Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.		Since sdaemon threads are a relatively scarce resource, it is usually not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.

			<p class="note"><b>Note:</b> If using any of the [[RKTools]] (SirMon, SirScan, SirPro, etc.), the minimum required <var>MAXDAEM</var> value is 10.</p>

	==See also==		==See also==

JDamon: Indicated minimum value of 10 for RKTools

2017-11-21T21:43:43Z

Indicated minimum value of 10 for RKTools

← Older revision		Revision as of 21:43, 21 November 2017
Line 9:		Line 9:
	<dd>User 0 CCAIN parameters		<dd>User 0 CCAIN parameters
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All.
			<p><b>NOTE:</b> If using any of the RKTools such as SIRMON, SIRSCAN, SIRPRO etc., the minimum required is MAXDAEM=10.</p>
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">[[Sirius Mods]]</var> Version 6.7		<dd><var class="product">[[Sirius Mods]]</var> Version 6.7

JAL: minor formatting

2016-11-07T17:54:01Z

minor formatting

← Older revision		Revision as of 17:54, 7 November 2016
Line 15:		Line 15:

	==Description==		==Description==
	This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by <var>[[~~New_~~(Daemon_constructor)\|New]]</var> method for <var>[[Daemon class\|Daemon]]</var> objects; or by a number of the (deprecated) Sirius ~~<var>~~[[~~List_of_~~$functions\|$functions]]~~</var>~~ such as: <var>[[$CommBg]]</var>, <var>[[$Command]]</var> or <var>[[$CommndL]]</var>.		This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by <var>[[New (Daemon_constructor)\|New]]</var> method for <var>[[Daemon class\|Daemon]]</var> objects; or by a number of the (deprecated) Sirius [[List of $functions\|$functions]] such as: <var>[[$CommBg]]</var>, <var>[[$Command]]</var> or <var>[[$CommndL]]</var>.

	Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.		Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.

JAL: add See also

2016-02-02T23:24:23Z

add See also

← Older revision		Revision as of 23:24, 2 February 2016
Line 13:		Line 13:
	<dd><var class="product">[[Sirius Mods]]</var> Version 6.7		<dd><var class="product">[[Sirius Mods]]</var> Version 6.7
	</dl>		</dl>

	==Description==		==Description==
	This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by <var>[[New_(Daemon_constructor)\|New]]</var> method for <var>[[~~Daemon_class~~\|Daemon]]</var> objects; or by a number of the (deprecated) Sirius <var>[[List_of_$functions\|$functions]]</var> such as: <var>[[$CommBg]]</var>, <var>[[$Command]]</var> or <var>[[$CommndL]]</var>.		This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by <var>[[New_(Daemon_constructor)\|New]]</var> method for <var>[[Daemon class\|Daemon]]</var> objects; or by a number of the (deprecated) Sirius <var>[[List_of_$functions\|$functions]]</var> such as: <var>[[$CommBg]]</var>, <var>[[$Command]]</var> or <var>[[$CommndL]]</var>.

	Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.		Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.

			==See also==
			<ul>
			<li>[[Daemons#Thread limits\|Thread limits]]</li>
			</ul>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:40:03Z

Automatically generated page update

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

JALWiccan: Automatically generated page update

2013-04-19T20:06:47Z

Automatically generated page update

← Older revision		Revision as of 20:06, 19 April 2013
Line 10:		Line 10:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Sirius Mods</var> Version 6.7		<dd><var class="product">[[Sirius Mods]]</var> Version 6.7
	</dl>		</dl>
	==Description==		==Description==

Dme at 19:27, 22 June 2012

2012-06-22T19:27:29Z

← Older revision		Revision as of 19:27, 22 June 2012
Line 16:		Line 16:

	Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.		Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.
	~~<!-- MAXINCL - PART OF BASE 204 NOW -->~~
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: 1 revision

2012-06-22T18:37:43Z

1 revision

← Older revision	Revision as of 18:37, 22 June 2012
(No difference)

Goff: edits, tags and links

2012-06-22T18:37:41Z

edits, tags and links

← Older revision		Revision as of 18:37, 22 June 2012
Line 10:		Line 10:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd>~~[[Sirius Mods\|~~"Sirius Mods~~"]]~~ Version 6.7		<dd><var class="product">Sirius Mods</var> Version 6.7
	</dl>		</dl>
	==Description==		==Description==

Goff: edits, tags and links

2011-04-22T07:00:00Z

edits, tags and links

New page

==Summary==
<dl>
<dt>Default value
<dd>1
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>[[Sirius Mods|"Sirius Mods"]] Version 6.7
</dl>
==Description==
This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by <var>[[New_(Daemon_constructor)|New]]</var> method for <var>[[Daemon_class|Daemon]]</var> objects; or by a number of the (deprecated) Sirius <var>[[List_of_$functions|$functions]]</var> such as: <var>[[$CommBg]]</var>, <var>[[$Command]]</var> or <var>[[$CommndL]]</var>.

Since sdaemon threads are a relatively scarce resource, it is not a good idea for a thread to use more than a handful of them at a time. Unfortunately, with <var>Daemon</var> objects, especially such objects embedded in another class, it is possible for a single runaway request to cause great problems by quickly consuming every daemon thread in an Online.

[[Category:System parameters]]
[[Category:Parameters]]