Splunk Enterprise Security

Should we lower acceleration.max_concurrent from 3 to ensure stability of the system?

danielbb
Motivator

For our accelerated datamodels,  acceleration.max_concurrent is set to 3 and we reach situations where lots of cpu is dedicated to the datamodel acceleration built-up. Should we lower acceleration.max_concurrent from 3 to protect the system?

Labels (1)
0 Karma

thambisetty
SplunkTrust
SplunkTrust

You might be having all searches scheduled at 15,30,45,60 minutes.

try to isolate them across an hour.

 

————————————
If this helps, give a like below.
0 Karma

richgalloway
SplunkTrust
SplunkTrust
In my experience, reducing the number made the accelerations take longer. I recommend leaving the setting as it is.
---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...