Performance reference for the Azure Storage Table input in the Splunk Add-on for Microsoft Cloud Services
The following is reference information about Splunk's performance testing of the Azure storage input in the Splunk Add-on for Microsoft Cloud Services. The testing occurred with version 2.0.0, when the Azure storage input was first introduced. Use this information to enhance the performance of your own Azure storage data collection tasks.
Many factors impact performance results, including file size, file compression, event size, deployment architecture, and hardware. These results represent reference information and do not represent performance in all environments.
Splunk tested the performance of the Storage input using a single-instance Splunk Enterprise 6.4.3 on an C4 High-CPU Double Extra Large instance to ensure CPU, memory, storage, and network do not introduce any bottlenecks. Instance specs:
The EC2 in the testing environment is in the same area of Azure storage input, the network latency is low.
|Instance type||C4 High-CPU Double Extra Large|
|Compute Units (ECU)||31 Unit|
|EBS Optimized: Max Bandwidth||1000 Mbps|
|Deployment Type||Role||EC2 Type||Count|
|Standalone Deployment||Standalone||C4 High-CPU Double Extra Large||1|
The detailed test result follows.
- The input number stands for the number of the inputs, one input collects one table.
- Each table contains 2,131,200 events.
- Each event is 500 Bytes.
|Input Number||Throughput (MB/s)||Throughput (GB/day)||Throughput (Event/s)|
The maximum throughput is 6.8MB/s with four data inputs. 100% higher than one data input. It can scale 100% with max throughput 577GB/day for single instance.
Performance reference for the Azure Event Hub input in the Splunk Add-on for Microsoft Cloud Services
Performance reference for the Azure Storage Blob input in the Splunk Add-on for Microsoft Cloud Services
This documentation applies to the following versions of Splunk® Supported Add-ons: released, released