Getting Data In

Are there practical limits to queue sizing on indexers?

twinspop
Influencer

We had an issue with parsing queue filling recently. Our oversized event profile is to blame. To address, I increased our queue size across the board to 100 MB from 50 MB. Is there any reason not to go higher? 1 GB? Given an indexer with unlimited RAM, is there a point of diminishing returns when it comes to queue sizing? Do the different queues have different PoDRs?

terminaloutcome
Path Finder

We've run pretty high queue sizes in the order of multiple gigabytes - but if you've got regular massive queues instead of short-term spikes you're probably focusing on the wrong problem. Ensure that you've sized your servers appropriately for the load, and tune the processing path to make sure you're not unnecessarily holding up data.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...