Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Monitoring Splunk
- :
- loadjob performance
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
SplunkTrust Application Period is Officially OPEN!
Announcing Modern Navigation: A New Era of Splunk User Experience
