Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2241
I don't think utilizing metrics consumer in TVL is the issue: it might
matter if results are close so that contributions of other system component
does matter, but it is just not acceptable latency for low rate. Huge gap
between twos.
Let's say we get rid of metrics consumer and that makes stable, then are we
going to pursue users to not use metrics consumer? That doesn't make sense.
While I don't think so, but if we think metrics consumer contributes throughput
and/or latency in really odd way, it needs to be validated and fixed.
As you can see my result, CPU was over 100% even with rate 500 and total
tasks of three key components were 12 (not 48, please keep in mind). All
results for TVL was captured in that way. So this patch shows high CPU usage in
baseline (say minimal load) and shows fluctuation by 80% all over rate 10000,
whereas master branch was 20%.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
