Threading - Revision history

Ubit: /* Jobs */

2020-10-22T21:29:26Z

‎Jobs

2020-10-22T21:29:04Z

‎Jobs

2020-10-22T21:28:48Z

‎Introduction

2020-10-22T21:28:29Z

‎Other thread pools

2020-10-22T21:27:53Z

‎Introduction

2020-10-22T21:22:29Z

‎Timers IO threads

2020-10-22T21:19:50Z

‎Thread pools

2020-10-22T21:19:22Z

‎Introduction

2020-10-22T21:17:42Z

‎Other thread pools

2020-10-22T21:17:09Z

‎Persistent threads

@@ Line 129: / Line 129: @@
 ==Jobs==
- A job is like a pool with a single thread. That thread is taken from the main generic pool, and returns to it when the job does not need it.
+A job is like a pool, or a sub-pool, with a single thread. That thread is taken from the main generic pool, and returns to it when the job does not need it.
 ==Other thread pools==

← Older revision		Revision as of 21:29, 22 October 2020
Line 129:		Line 129:

	==Jobs==		==Jobs==
		+	A job is like a pool with a single thread. That thread is taken from the main generic pool, and returns to it when the job does not need it.

	==Other thread pools==		==Other thread pools==

@@ Line 5: / Line 5: @@
 # Persistent threads. Threads which are continually used for the same task and not returned to any kind of pooling mechanism.
 # Thread pools.
-# Jobs. A job is like a pool with a single thread. That thread is taken from the main generic pool, and returns to it when the job does not need it
+# Jobs.
 # Timer events or IO threads.
 # Tasks.

← Older revision		Revision as of 21:28, 22 October 2020
Line 127:		Line 127:

	In this case there are two regions, MyRegion1 and MyRegion2, and hence two thread pools. The thread pool details are the lines which match the data given for the general thread pool (Unique scripts, allocated threads, etc.). In this case, the "xengine status" command also shows additional details (scripts loaded, sensors, etc.) which are not directly thread related.		In this case there are two regions, MyRegion1 and MyRegion2, and hence two thread pools. The thread pool details are the lines which match the data given for the general thread pool (Unique scripts, allocated threads, etc.). In this case, the "xengine status" command also shows additional details (scripts loaded, sensors, etc.) which are not directly thread related.
		+
		+	==Jobs==

	==Other thread pools==		==Other thread pools==

@@ Line 5: / Line 5: @@
 # Persistent threads. Threads which are continually used for the same task and not returned to any kind of pooling mechanism.
 # Thread pools.
-# Jobs. A job is like a pool with a single thread. That thread is taken from main generic Pool, and returns to it when the job does not need it
+# Jobs. A job is like a pool with a single thread. That thread is taken from the main generic pool, and returns to it when the job does not need it
 # Timer events or IO threads.
 # Tasks.

@@ Line 132: / Line 132: @@
 Additional SmartThreadPool instances used on several modules.
-==Timers IO threads==
+==Timers and IO threads==
 This are threads from .Net main Threadpool.<br>

@@ Line 60: / Line 60: @@
 =Thread pools=
-A thread is a expensive program resource that takes a lot of time to create and release. A thread pool allows a reduction of the number of suck operations, reusing a thread while it is needed.<br>
+A thread is a expensive program resource that takes a lot of time to create and release. A thread pool allows a reduction of the number of such operations, reusing a thread while it is needed.<br>
 Instead of releasing a thread once a job is done, the thread is kept on a pool for sometime, and only released if was not needed during that time<br>
 The pool may keep a minimum number of threads, so a new work item does not need to wait for the time it takes to create a new thread.<br>

@@ Line 56: / Line 56: @@
 * '''Outcoming Packets (<region-name>)''' - Sends queued outgoing LLUDP protocol packets to viewers.  One per region.
 * '''AsyncLSLCmdHandlerThread''' - Performs asynchronous processing related to various scripting facilities.  This currently covers dataserver requests, timer firing, HTTP operations, listeners, sensors and XMLRPC requests.  Currently, one per simulator.
 =Thread pools=