Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2829
@arunmahadevan I think the reason for only emitting one tuple at a time was
to let Storm enforce the max.spout.pending limit. Maybe it would be better to
accept some overflow in order to get the spout running faster, since people can
still control how large the overflow can get by setting the consumer's
max.poll.records (which I don't believe existed at the time the spout was
originally written). I wanted to point to the PR where this was discussed, but
I can't find it.
If you want to try emitting as many tuples as possible, it should be
possible by removing this break:
https://github.com/apache/storm/pull/2829/files#diff-7d7cbc8f5444fa7ada7962033fc31c5eR425
+1 for the current changes.
---
