Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1362#issuecomment-214781229
I've done performance comparison test with ThroughputVsLatency with one
machine.
* disruptor batching size is set to default (100 / timeout 1ms)
throughput | version | min | max | mean | stddev | 99% | 99.9%
---- | ---- | ---- | ---- | ---- | ---- | ---- | ----
10000 | before patch | 9,437,184 | 23,609,343 | 16,875,865.63 |
1,342,051.21 | 19,611,647 | 20,987,903
10000 | STORM-1731 | 9,273,344 | 23,609,343 | 16,639,346.99 | 1,401,096.42
| 19,333,119 | 20,660,223
22000 | before patch | 9,134,080 | 157,155,327 | 18,968,494.02 |
13,125,204.89 | 95,551,487 | 27,729,663
22000 | STORM-1731 | 8,871,936 | 27,869,183 | 16,865,395.47 | 1,306,652.91
| 19,660,799 | 21,233,663
At throughput 22,000, latency increases steeply from version 'before
patch', but latency increases relatively really small from version 'STORM-1731'.
I will go on tests with throughput 25000, 30000 and post the results, too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
