Monitoring Flume's performance over time is an important step in every
production-level application. Benchmarking Flume on a nightly basis has
the following advantages:
* Better understanding of Flume's bottlenecks.
* Allow users to compare the performance of different solutions, such as
Logstash and Fluentd.
* Better understanding of the influence of recent commits on performance.
Logstash already conducts various performance tests, more details in this
I propose adding a few micro-benchmarks showing Flume's TPS vs date (of
course, in the ideal case where the input and/or output do not bottleneck
the system), e.g. using the SeqGen source.