2021:Thread Pool (Object) - Revision history

Dgreenwood at 19:24, 5 February 2026

2026-02-05T19:24:45Z

← Older revision		Revision as of 14:24, 5 February 2026
Line 6:		Line 6:
	'''!!'''		'''!!'''
	\|		\|
	'''''LEGACY TECHNOLOGY DETECTED!'''''		'''''LEGACY TECHNOLOGY DETECTED!!'''''

	In version 2022, the '''Thread Pool''' object was replaced by the '''Processing Queue''' object.		In version 2022, the '''Thread Pool''' object was replaced by the '''Processing Queue''' object.

Dgreenwood at 19:24, 5 February 2026

2026-02-05T19:24:29Z

← Older revision		Revision as of 14:24, 5 February 2026
Line 1:		Line 1:
	__NOINDEX__		__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}
	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px~~"		{\|class="important-box"
	\|-		\|-
	\|~~style="font-size:125%; background-color:#36b0a7; color:white; width:28px; text-align:center"~~\|'''~~FYI~~'''		\|
	~~\|style="border: 4px solid #36b0a7"\|~~		'''!!'''
	In version 2022, the '''Thread Pool''' object was ~~re-envisioned as~~ the '''Processing Queue''' object. For more information on '''Processing Queues''', [[Processing Queue\|visit this article]].		\|
			'''''LEGACY TECHNOLOGY DETECTED!'''''

			In version 2022, the '''Thread Pool''' object was replaced by the '''Processing Queue''' object.

			For more information on '''Processing Queues''', [[Processing Queue\|visit this article]].
	\|}		\|}

Dgreenwood at 19:22, 5 February 2026

2026-02-05T19:22:51Z

← Older revision		Revision as of 14:22, 5 February 2026
Line 32:		Line 32:

	[[Category:Articles]]		[[Category:Articles]]
	~~[[Category:Stub]]~~

	<!---EDITOR'S NOTE		<!---EDITOR'S NOTE

Dgreenwood at 16:12, 5 August 2025

2025-08-05T16:12:31Z

← Older revision		Revision as of 11:12, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}
	{\|cellpadding="10" cellspacing="5" style="margin:12px"		{\|cellpadding="10" cellspacing="5" style="margin:12px"

Dgreenwood at 17:17, 3 March 2025

2025-03-03T17:17:14Z

← Older revision		Revision as of 12:17, 3 March 2025
Line 15:		Line 15:
	== About ==		== About ==

	Some activities only allow one instance of the activity to execute at a time per machine executing the activity (For example the '''[[~~Render (Activity)\|~~Render]]''' activity). In such case, you would first create a new '''Thread Pool''', specifying a ''PerMachine'' for the '''''Concurrency Mode''''' property. Then, you would create an '''Activity Processing''' service, assign it the newly created '''Thread Pool''' and drop the number of available threads to ''one''. Last, you would configure the activity's step in the '''Batch Process''' to run using the newly created '''Thread Pool''' instead of the "Default". By doing this, the activity will be forced to run on a single thread, one instance at a time, one server or workstation at a time. If another instance of that activity tries to run while the first is running (such as a second '''Batch''' running on the same machine trying to run the same activity already running in another '''Batch Process'''), the second will be forced to wait its turn.		Some activities only allow one instance of the activity to execute at a time per machine executing the activity (For example the '''[[Render]]''' activity). In such case, you would first create a new '''Thread Pool''', specifying a ''PerMachine'' for the '''''Concurrency Mode''''' property. Then, you would create an '''Activity Processing''' service, assign it the newly created '''Thread Pool''' and drop the number of available threads to ''one''. Last, you would configure the activity's step in the '''Batch Process''' to run using the newly created '''Thread Pool''' instead of the "Default". By doing this, the activity will be forced to run on a single thread, one instance at a time, one server or workstation at a time. If another instance of that activity tries to run while the first is running (such as a second '''Batch''' running on the same machine trying to run the same activity already running in another '''Batch Process'''), the second will be forced to wait its turn.

	'''Thread Pools''' are also used to control the concurrency of operations to an external system. Imagine you are exporting to a content management system using a '''[[CMIS Connection]]'''. Assume your system has 64 threads available for processing. If the content management system allows 64 concurrent connections (allowing 64 documents exporting at a time in this case), then there's no problem. The system has one thread for each document exporting to the content management system. The '''[[Export]]''' activity would run with no problems. However, what if the content management system only allows for 16 connections at a time? Grooper is going to try and use ''all'' 64 threads to export unless told otherwise. The first 16 documents might export with no problems, but the next 48 (64 threads minus 16 threads) will error out. By creating a '''Thread Pool''' using only 16 threads for the '''Export''' activity, Grooper will hold off from using all 64 threads for the activity. Only 16 threads, one for each allowable concurrent connection to the content management system, will be used at a time.		'''Thread Pools''' are also used to control the concurrency of operations to an external system. Imagine you are exporting to a content management system using a '''[[CMIS Connection]]'''. Assume your system has 64 threads available for processing. If the content management system allows 64 concurrent connections (allowing 64 documents exporting at a time in this case), then there's no problem. The system has one thread for each document exporting to the content management system. The '''[[Export]]''' activity would run with no problems. However, what if the content management system only allows for 16 connections at a time? Grooper is going to try and use ''all'' 64 threads to export unless told otherwise. The first 16 documents might export with no problems, but the next 48 (64 threads minus 16 threads) will error out. By creating a '''Thread Pool''' using only 16 threads for the '''Export''' activity, Grooper will hold off from using all 64 threads for the activity. Only 16 threads, one for each allowable concurrent connection to the content management system, will be used at a time.

Randallkinard: Randallkinard moved page 2021:Thread Pool to 2021:Thread Pool (Object) without leaving a redirect: new naming convention

2024-04-18T17:35:36Z

Randallkinard moved page 2021:Thread Pool to 2021:Thread Pool (Object) without leaving a redirect: new naming convention

← Older revision	Revision as of 12:35, 18 April 2024
(No difference)

Dgreenwood: Dgreenwood moved page Thread Pool to 2021:Thread Pool

2024-01-09T17:53:26Z

Dgreenwood moved page Thread Pool to 2021:Thread Pool

← Older revision	Revision as of 12:53, 9 January 2024
(No difference)

Dgreenwood at 17:53, 9 January 2024

2024-01-09T17:53:13Z

← Older revision		Revision as of 12:53, 9 January 2024
Line 1:		Line 1:
	{{~~Auto Version~~}}		{{AutoVersion}}
	{\|cellpadding="10" cellspacing="5" style="margin:12px"		{\|cellpadding="10" cellspacing="5" style="margin:12px"
	\|-		\|-
Line 12:		Line 12:

	New [[Grooper Repository\|Grooper Repositories]] initialize with a single '''Thread Pool''' named "Default". In many cases, this is sufficient to run all activities. However, one can alter how many processing [[Thread\|threads]] are allocated to an activity in a '''[[Batch Process]]'''. This is done by creating a new '''Thread Pool''', assigning it to an '''[[Activity Processing]]''' Grooper Service from [[Grooper Config]], specifying how many threads that '''Thread Pool''' should use, and referencing the '''Thread Pool''' on that activity's '''Batch Step''' properties.		New [[Grooper Repository\|Grooper Repositories]] initialize with a single '''Thread Pool''' named "Default". In many cases, this is sufficient to run all activities. However, one can alter how many processing [[Thread\|threads]] are allocated to an activity in a '''[[Batch Process]]'''. This is done by creating a new '''Thread Pool''', assigning it to an '''[[Activity Processing]]''' Grooper Service from [[Grooper Config]], specifying how many threads that '''Thread Pool''' should use, and referencing the '''Thread Pool''' on that activity's '''Batch Step''' properties.
	~~</onlyinclude>~~
	== About ==		== About ==

Dgreenwood at 17:53, 9 January 2024

2024-01-09T17:53:01Z

← Older revision		Revision as of 12:53, 9 January 2024
Line 1:		Line 1:
			{{Auto Version}}
	{\|cellpadding="10" cellspacing="5" style="margin:12px"		{\|cellpadding="10" cellspacing="5" style="margin:12px"
	\|-		\|-
Line 5:		Line 6:
	In version 2022, the '''Thread Pool''' object was re-envisioned as the '''Processing Queue''' object. For more information on '''Processing Queues''', [[Processing Queue\|visit this article]].		In version 2022, the '''Thread Pool''' object was re-envisioned as the '''Processing Queue''' object. For more information on '''Processing Queues''', [[Processing Queue\|visit this article]].
	\|}		\|}
	~~<onlyinclude>~~
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	'''Thread Pools''' allow Grooper to allocate system resources to different '''[[Activity\|Unattended Activities]]'''.		'''Thread Pools''' allow Grooper to allocate system resources to different '''[[Activity\|Unattended Activities]]'''.

Dgreenwood at 21:43, 22 September 2023

2023-09-22T21:43:34Z

← Older revision		Revision as of 16:43, 22 September 2023
Line 19:		Line 19:

	More detailed information about how to add a new '''Thread Pool''' and assign it to an '''Activity Processing''' service can be found in the [[Activity Processing]] article.		More detailed information about how to add a new '''Thread Pool''' and assign it to an '''Activity Processing''' service can be found in the [[Activity Processing]] article.

			=== Concurrency Mode ===

			This property specifies the parallel processing mode for a '''Thread Pool'''. It controls how multiple '''Activities''' (or the machines processing '''Activities''') pool system resources.

			This can be set to one of three modes:
			* ''Multiple'' - Multiple instances can run concurrently. Multiple occurrences of the '''Activities''' using the '''Thread Pool''' can run at the same time
			* ''PerMachine'' - Only a single instance can run on a single machine. Only one occurrence of an activity can run on a machine at a time.
			* ''Single'' -Only a single instance can run per [[Grooper Repository]]. Regardless of how many machines are connected to the repository attempting to run an activity, only one occurrence of an activity using the '''Thread Pool''' can run at a time.

			[[Category:Articles]]
			[[Category:Stub]]

			<!---EDITOR'S NOTE
			Ensure this information is adequately explained in the Thread Pool/Processing Queue articles. Then, delete this article.


	[[Category:Articles]]		[[Category:Articles]]