CI Reference Lookup Extremely Slow with Large CMDB (~2.3M CIs)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
We are experiencing severe performance issues with the Configuration Item (CI) reference lookup when clicking the magnifying glass from Incident and Change records.
Our CMDB contains approximately 2.3 million CIs, and simply opening the CI lookup takes a long time to load. This delay occurs before any manual filtering or paging is applied and is significantly impacting Incident and Change workflows where CI selection is frequent.
We are trying to understand the correct approach to improve CI reference lookup performance at this scale.
Question:
For large CMDBs, can modifying the out-of-box CI reference qualifier help reduce the load time when opening the CI lookup, or are there recommended approaches specifically for improving CI search performance at this scale?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
@SubramaniP Out of all the 2.3 million CIs, would you be raising Incident/Change on all classes of CMDB. If not, you can make some of the classes as Primary. If you think most of the CIs Incident/change raised belong to Windows Server/Computer/Servers/VMs, then you can make these classes as primary. When you do that, only the CIs from these classes will be populated.
Please go through below article on how to set a class as primary -
How to Set Principal Classes for ITSM - ServiceNow Community
