Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/2241
@roshannaik sorry I just reread your other post and it looks like I missed
some of your questions.
`topology.producer.batch.size` and `topology.flush.tuple.freq.millis` are
what ever the default values are. I didn't modify them. I am happy to explore
the settings there too, but I just have not spent time on it, it just may take
me a few days as I have other work to do too.
I agree that when we throttle the spout it is not able to truly gauge the
maximum throughput possible. TVL was not designed for that is why the latency
measurements are based off of a simulation of when a message would have been
inserted into something like kafka instead of when the message arrived in the
spout. If you do set the desired throughput higher than what the topology can
handle you are able to get an idea of what the maximum throughput is, but other
measurements are likely to be off so it is of limited value for what I was
trying.
---
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.
---
