Getting Data In

Poor indexing rate in indexer

mwong
Splunk Employee
Splunk Employee

In SoS app, it is found that the indexing rate is limited to about 200Kb/s.

Tags (1)
0 Karma

mwong
Splunk Employee
Splunk Employee

Sometimes a forwarder app is accidentally deployed to an indexer. It is normally limited by the throughput of network bandwidth.

[thruput]
maxKBps = 256

Please try to use the command ./splunk cmd btool limits list thruput to check if the maxKBps is set to 0. Otherwise indexing rate of an indexer will be limited and not fully utilized the IO rate of the disk system.

You may also refer the link below showing that index_thruput is controlled by thruput value.
http://wiki.splunk.com/Community:HowIndexingWorks

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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...