ITSI module performance and sizing guidelines

This topic discusses performance and sizing guidelines for the ITSI modules.

Performance requirements

ITSI modules do not have specific performance and sizing requirements. As they correlate data that ITSI receives, focus on configuring the forwarding and indexing tiers of your ITSI deployment to send and receive data as quickly as possible.

Of particular importance in providing the best performance for the module is confirming that the add-ons that provide the data for the module have been properly scaled. While the only performance overhead in this regard is the universal forwarder, you must understand how network, disk, and performance factors can impact data collection. Network, disk, or CPU congestion can result in the late arrival of data. This manifests itself in being unable to locate host data to define entities or services.

Typical daily indexing volume

The following table details the typical rate of data that the Splunk Add-ons for Windows and Unix and Linux collect per host, per day for correlation with the ITSI modules. The actual amount of data that the add-ons collect might vary depending on several factors including the role and amount of computing activity of each host.

Index	Windows	Unix and Linux
wineventlog	27MB	N/A
windows	2MB	N/A
perfmon	28MB	N/A
os	N/A	36MB
firedalerts	N/A	24MB