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
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.


Introducing Unified TDIR with the New Enterprise Security 8.2

Read the blog
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...