Hi ZhangChi, It may have issue if many topics co-exist in the same spout because each nextTuple() may take time. The original design has considered the scenario of many topics, for example it can be solved by deploying multiple storm topology to solve.
Can you use more task nodes for the spout if your data has been partitioned well? Thanks Edward On Fri, May 17, 2019 at 9:04 AM [email protected] <[email protected]> wrote: > 我遇到了一个性能问题，当spout从多个kafka > topic订阅消息时，将存在性能问题。每个topic无法达到40000TPS的性能瓶颈。我分析是一下代码的问题，发现这段循环会随着topic数量的增加而线性的下降。请问在设计的时候是否有过这方面的考虑，应该如何解决？ > > ------------------------------ > *张驰* > 组织结构：应用技术部-渠道管理组 > 联系电话：18511460690 >
