Background Queues and Platform Performance
Introduction | Recommended Configurations | Video | Additional Concepts
Introduction
The Recommended Configurations are captured below.
To understand the rationale for the Recommended Configurations, please see the video below. It also explains how to:
eliminate any impact Discovery Admin may have on your ServiceNow Instance
proactively manage resource contention for your ServiceNow Platform
Recommended Configurations (for Production)
Navigate to:
Table: sys_trigger
Search for the following Background Queues:
x_qune_da_ea_st: Scheduled Troubleshooting Standard Queue
x_qune_da_gi_st: Scheduled Incident Generation Standard Queue
Set the Attribute (for both the Background Queues):
priority = 500
Video (6 mins :: 13 seconds)
 Additional Concepts
Background Queues are used to eliminate any performance impact of Discovery Admin on the ServiceNow Platform in the following ways:
Discovery Admin runs in the background, leveraging these Background Queues. As a result, by design, this eliminates the impact on the End User Experience via the ServiceNow UI.
Discovery Admin uses Background Queues in the Discovery Admin Scope (vs the Global Scope). Since ServiceNow automatically throttles the Discovery Admin Background Queue (giving preference to the Global Scope), this eliminates impact on other out-of-the-box background processes (eg. ServiceNow Discovery, Email Notification, etc).
Discovery Admin has a limited number of Background Queues that can actively run simultaneously, resulting in a limit for the maximum number of threads/semaphores that Discovery Admin can use. As a result, this eliminates the impact on other processes on ServiceNow which may need additional threads to run.