Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property configures the number of parallel job workers that can be utilized during Data Discovery processes, enhancing efficiency in data scanning. |
| What area does it affect? |
Data Discovery performance |
| What does the default mean? |
No default value is stated in the ServiceNow documentation. |
| When should you review it? |
Review this property when optimizing Data Discovery job execution or adjusting system performance. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
com.glide.data_discovery.max_concurrent_item_workers |
| Type |
Not stated |
| Application |
Not stated |
| Default value |
Not stated |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... default Data Discovery runs jobs using a single thread. Multiple threads may be activated for Data Discovery full scans. 1. In the navigation filter enter sys_properties.list. 2. Create the property com.glide.data_discovery.max_concurrent_item_workers 3. Verify the Type is integer. 4. Important: It is recommended to start with a small number of workers per node(2 or 3. Enter the number of parallel job workers ...
More in com.glide
Other properties in the same namespace.
All 831 properties in com.glide →