MAXDAEM parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (edits, tags and links)
 
m (move RKTools note)
 
(8 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Template:MAXDAEM parameter subtitle}}
==Summary==
==Summary==
<dl>
<dl>
<dt>Default value
<dt>Default value
<dd>1
<dd>1  
<dt>Parameter type
<dt>Parameter type
<dd>System
<dd>System
Line 10: Line 11:
<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==
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 [[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 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==
<ul>
<li>[[Daemons#Thread limits|Thread limits]]</li>
</ul>


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]]

Latest revision as of 16:57, 22 November 2017

Maximum Daemon objects per user

Summary

Default value
1
Parameter type
System
Where set
User 0 CCAIN parameters
Related products
All
Introduced
Sirius Mods Version 6.7

Description

This parameter indicates the maximum number of sdaemon threads that can be used by an individual thread. Such threads are allocated by New method for Daemon objects; or by a number of the (deprecated) $functions such as: $CommBg, $Command or $CommndL.

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 Daemon 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.

Note: If using any of the RKTools (SirMon, SirScan, SirPro, etc.), the minimum required MAXDAEM value is 10.

See also