CyJaySong opened a new issue #668: URL: https://github.com/apache/pulsar-client-go/issues/668
#### Expected behavior The load of the cpu is less affected by the number of topic partitions #### Actual behavior I have a project deployed on a server， The RocketMQ (also deployed on this server) was used as a message queue. During the peak of the business, the CPU usage of the server was only 12%. When I After replacing the message queue with Tencent's TDMQ-Pulsar service, the CPU usage of my service became very high. In the past, each topic on RocketMQ I built by myself had 16 partitions, while each topic of TDMQ-Pulsar only had 4 partitions, but the CPU usage is still 4 times the previous. Even if I adjust the number of partitions for each topic to 1, the CPU usage still exceeds that of the RocketMQ version. pprof concluded that runtime.netpoll occupies too much CPU. #### Steps to reproduce Create a topic, set the number of partitions to 1, use producers and consumers to connect to it in the service, view and record the CPU usage. Increase the number of partitions of the topic, connect to it again, check the CPU usage and compare with the previous results. #### System configuration **Pulsar version**: 2.7 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
