2023.1:Grooper Infrastructure - Revision history

Dgreenwood: Dgreenwood moved page 2023.1:Grooper Infrastructure (Concept) to 2023.1:Grooper Infrastructure without leaving a redirect

2026-01-08T17:27:11Z

Dgreenwood moved page 2023.1:Grooper Infrastructure (Concept) to 2023.1:Grooper Infrastructure without leaving a redirect

← Older revision	Revision as of 12:27, 8 January 2026
(No difference)

Dgreenwood: /* The Database */

2024-10-28T18:35:27Z

The Database

Show changes

Dgreenwood: /* The Database */

2024-10-25T17:32:50Z

The Database

← Older revision		Revision as of 12:32, 25 October 2024
Line 165:		Line 165:
	<tabs>		<tabs>
	<tab name="Grooper 2024">		<tab name="Grooper 2024">
			''Please note the Grooper database tables are not listed here in alphabetical order. They are listed in terms of how impactful they are to Grooper's overall architecture.''

	<big>'''dbo.TreeNode'''</big>		<big>'''dbo.TreeNode'''</big>

Dgreenwood: /* The Database */

2024-10-25T17:31:07Z

The Database

@@ Line 192: / Line 192: @@
 |-
 | LastModified || datetime2 || 8 || Indicates the most recent date and time the node was modified. Used by various Grooper processes that need to know when a node has been changed. This is a more precise replacement for the ''RowVersion'' column in previous Grooper versions.
 |}
@@ Line 312: / Line 262: @@
 |-
 | Completed || datetime || 8 || date/time when the task completed
 |}

Dgreenwood: /* The Database */

2024-10-25T17:30:01Z

The Database

← Older revision		Revision as of 12:30, 25 October 2024
Line 191:		Line 191:
	\| NodeValues \|\| varchar(MAX) \|\| -1 \|\| Metadata about the node that pertains to '''Grooper''' modules (Seldom used, except by custom scripting).		\| NodeValues \|\| varchar(MAX) \|\| -1 \|\| Metadata about the node that pertains to '''Grooper''' modules (Seldom used, except by custom scripting).
	\|-		\|-
	\| LastModified \|\| datetime2 \|\| 8 \|\| Indicates the ~~last~~ date and time the node was modified. Used ~~for search indexing purposes~~. This is a more precise replacement for the ''RowVersion'' column in previous Grooper versions.		\| LastModified \|\| datetime2 \|\| 8 \|\| Indicates the most recent date and time the node was modified. Used by various Grooper processes that need to know when a node has been changed. This is a more precise replacement for the ''RowVersion'' column in previous Grooper versions.
	\|}		\|}

Dgreenwood: /* The Database */

2024-10-25T17:27:53Z

The Database

Show changes

Dgreenwood: /* About thread allocation for Grooper services */

2024-10-02T15:15:00Z

About thread allocation for Grooper services

← Older revision		Revision as of 10:15, 2 October 2024
Line 124:		Line 124:
	* If IIS ''and'' SQL are installed on the same machine as your Grooper services, you should follow an "n minus three" rule, reserving one for the OS, one for SQL, and one for IIS.		* If IIS ''and'' SQL are installed on the same machine as your Grooper services, you should follow an "n minus three" rule, reserving one for the OS, one for SQL, and one for IIS.
	* If ''other'' applications, such as anti-virus software, are running in the background you will need to reserve threads for those applications as well.		* If ''other'' applications, such as anti-virus software, are running in the background you will need to reserve threads for those applications as well.
			* ''This is one of the many reasons why we recommend distributing SQL, IIS, and processing services across multiple machines.''

	'''''THE LONG STORY SHORT HERE IS DO NOT OVER-ALLOCATE YOUR AVAILABLE THREADS! GROOPER CAN BEHAVE ERRATICALLY IF YOU DO!'''''		'''''THE LONG STORY SHORT HERE IS DO NOT OVER-ALLOCATE YOUR AVAILABLE THREADS! GROOPER CAN BEHAVE ERRATICALLY IF YOU DO!'''''

Dgreenwood: /* About thread allocation for Grooper services */

2024-10-02T15:12:36Z

About thread allocation for Grooper services

← Older revision		Revision as of 10:12, 2 October 2024
Line 105:		Line 105:
	<big><b><u>[[:file:SystemArchitecture_2023_lightMode.png\|Click here for a "light mode" version of the above image]]</b></u></big>		<big><b><u>[[:file:SystemArchitecture_2023_lightMode.png\|Click here for a "light mode" version of the above image]]</b></u></big>

	=== About thread allocation for Grooper services ===		== About thread allocation for Grooper services ==

	'''Be aware of the "n minus one" rule!'''		'''Be aware of the "n minus one" rule!'''

Dgreenwood: /* System Architecture and Requirements */

2024-10-02T15:12:23Z

System Architecture and Requirements

← Older revision		Revision as of 10:12, 2 October 2024
Line 104:		Line 104:

	<big><b><u>[[:file:SystemArchitecture_2023_lightMode.png\|Click here for a "light mode" version of the above image]]</b></u></big>		<big><b><u>[[:file:SystemArchitecture_2023_lightMode.png\|Click here for a "light mode" version of the above image]]</b></u></big>

			=== About thread allocation for Grooper services ===

			'''Be aware of the "n minus one" rule!'''

			Services are assigned a number of CPU threads when you install them. For some services, like '''Import Watcher''', the will always run using a single thread. '''Activity Processing''' services can run using multiple threads.

			Keep in mind, your machine only has a certain number of processing threads available. You '''''will''''' run into errors if you over-allocate your available threads.

			Remember too, the operating system itself must always have a single thread available to run. So, the absolute maximum number of threads you can assign to all your services '''''should not''''' go beyond the total number of threads available minus one reserved for the operating system. Hence, the "n minus one" rule.

			The "n minus one" rule is as follows:
			* If "n" is the maximum number of threads available on your machine, the maximum number of threads you can distribute to Grooper services is "n" minus one.

			'''Be aware of the "n minus x" rule!'''

			Other programs running in the background will need threads to run as well.
			* If SQL is installed on the same machine as your Grooper services, you should follow an "n minus two" rule, reserving one for the OS and one for SQL.
			* If IIS ''and'' SQL are installed on the same machine as your Grooper services, you should follow an "n minus three" rule, reserving one for the OS, one for SQL, and one for IIS.
			* If ''other'' applications, such as anti-virus software, are running in the background you will need to reserve threads for those applications as well.

			'''''THE LONG STORY SHORT HERE IS DO NOT OVER-ALLOCATE YOUR AVAILABLE THREADS! GROOPER CAN BEHAVE ERRATICALLY IF YOU DO!'''''

	== Cloud Deployment Guidance ==		== Cloud Deployment Guidance ==

Randallkinard: Randallkinard moved page Grooper Infrastructure (Concept) to 2023.1:Grooper Infrastructure (Concept)

2024-08-28T15:56:43Z

Randallkinard moved page Grooper Infrastructure (Concept) to 2023.1:Grooper Infrastructure (Concept)

← Older revision	Revision as of 10:56, 28 August 2024
(No difference)