All Apps and Add-ons

Common Information Model (CIM) Performance Tuning

kernand0
Loves-to-Learn

Hello. 

Our organization has one of our Data Model (DM) searches for ES regularly running over 200 seconds to complete.  Soon another source will be added to the DM, so I have been looking for ways to reduce the runtime.  

I came across a site that suggested the macros that build the CIM DM's could be faster by adding the sourcetype alongside the index in the search.  My thought was, "Why stop there?"  You could add the source too, as long as it doesn't iterate with a date or some random number scheme.  And even then, with reasonable wildcarding at the end I believe there would be a performance improvement.

I was told that this effort is unnecessary, even though in my unofficial tests over the same period, I found my modified searches to nearly twice as fast.  So aside from the additional effort to build those searches and maintain them, why is this unnecessary?  

Thanks
AJ

Labels (2)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...