Splunk Stream

Installation and Configuration Manual

This documentation does not apply to the most recent version of Splunk Stream. For documentation on the most recent version, go to the latest release.

Stream forwarder sizing guide

The maximum number of Stream forwarders (streamfwd) that a search head can support depends on the value of the pingInterval parameter in streamfwd.conf. Based on our tests, a single search head running splunk_app_stream can process approximately 150 pings + stream configuration requests per second.

Use this formula to calculate the maximum number of Stream forwarders per search head:

Stream forwarders per search head = 150 * pingInterval

The default pingInterval setting is 5 seconds, so a single search head can run up to 750 Stream Forwarders at peak activity (during startup up or when stream configuration changes are made).

Based on our tests, during average usage, a single search head running splunk_app_stream can process approximately 400 ping requests/second. However, the startup load on the CPU is significantly higher because streamfwd must both send a ping request and pull down the full configuration from splunk_app_stream.

If your deployment includes large numbers of Stream forwarders, we suggest that you run splunk_app_stream on a dedicated server AND stagger the startup of individual Stream forwarders over time. Starting up too many Stream forwarders simultaneously might overload the server.

Last modified on 29 March, 2018
Flow collector performance test results   Splunk Stream REST API reference

This documentation applies to the following versions of Splunk Stream: 7.1.0, 7.1.1


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters