---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Adjust the scale factor for Event Framework jobs

# Adjust the scale factor for Event Framework jobs {#ariaid-title1}

* Release version: Australia
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Adjust the scale factor to modify the number of worker threads per app node, which increases or decreases throughput.

## Before you begin

Confirm the following:

* Discovery Admin Workspace is using version 1.9.0 or later.
* ServiceNow AI Platform® is using version XP9, YP4, or later than YP4.
* The discovery.use.event.processing system property is turned on. For more information, see [Configure Discovery to use Event Framework](https://www.servicenow.com/docs/ONWWI_xmfIlW3bznIJliQQ "Configure Discovery to process jobs using the Event Framework method, which enables you to manage discovery throttling effectively and prioritize tasks based on their importance in the queue.").
* The Job configuration type field of the Queue Registration form is set to Scale with nodes. For more information, see [Queue Registration form reference](https://www.servicenow.com/docs/NuCx_KEEWgEMzkfUuTpdcg "The Queue Registration form displays the fields available when creating or modifying a queue.").
{#t_AjustScaleFactorEF__ul_m31_scl_b1c}

Role required: discovery_admin

## About this task

If your instance becomes slow while Discovery is running, you can adjust the scale factor to modify the number of worker threads per app node. The default scale factor is set to 2, which corresponds to two worker threads per app node.

For example, if you increase the scale factor to 3, Discovery uses three worker threads per app node, increasing throughput. Conversely, reducing the scale factor to 1 limits Discovery to a single worker thread per app node, which decreases throughput.

## Procedure

1. Navigate to AllSystem PolicyQueue Registry.
2. Choose one or more job types for which you want to adjust the scale factor.

   | Job type | Action |
   | IP-based | Select discovery.sensors from the Queue Registry \[sysevent_queue\] table. |
   | Cloud-based | Select discovery.cloud.sensors from the Queue Registry \[sysevent_queue\] table. |
   |-|-|

   {#t_AjustScaleFactorEF__choicetable_ntt_zjg_gfc}
3. In the Scale factor field, set a value.  
   Note:  
   The default maximum value is 3. To increase the scale factor beyond 3, configure the com.glide.processing.framework.max_thread_utilization_percentage property. For more information about this property, see [Discovery properties](https://www.servicenow.com/docs/0irr66vIpUl6GxbWD~edYg "Discovery properties allow you to control several aspects of the horizontal discovery process."). For instructions on how to create a property, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US).
4. Select Update.

*[\>]: and then