Monitoring Splunk

loadjob performance

rettops
Path Finder

What determines the performance of loading the artifacts of a savedsearch? I have a job which ran a savedsearch, and it has 70,000 results. Doing a 'loadjob' on the sid of that job takes 10 seconds. What could cause it to take so long?

Tags (2)
1 Solution

LukeMurphey
Champion

loadjob streams the contents of the dispatch directory for the given search into memory before executing. Thus, performance can vary based upon the size of the dispatch directory and the IO performance of your disks.

If you are not using 5.0.2 or later, then you may find performance improves if you upgrade. Before 5.0.2, loadjob used to load the dispatch directory for the search into memory all at once. Thus, using loadjob for a search with a 1 GB dispatch directory would use up 1 GB of memory. This could cause a significant reduction in performance. In 5.0.2, the contents are streamed so that the entire directory is not in memory all at once; this is much more performant.

View solution in original post

LukeMurphey
Champion

loadjob streams the contents of the dispatch directory for the given search into memory before executing. Thus, performance can vary based upon the size of the dispatch directory and the IO performance of your disks.

If you are not using 5.0.2 or later, then you may find performance improves if you upgrade. Before 5.0.2, loadjob used to load the dispatch directory for the search into memory all at once. Thus, using loadjob for a search with a 1 GB dispatch directory would use up 1 GB of memory. This could cause a significant reduction in performance. In 5.0.2, the contents are streamed so that the entire directory is not in memory all at once; this is much more performant.

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!

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...