iNanos opened a new issue #471: URL: https://github.com/apache/incubator-eventmesh/issues/471
## Enhancement Request ### Is your enhancement request related to a problem? Please describe EventMesh currently chooses a consumer group-level agent, that is, there is only one real Consumer on a single EventMesh instance of a consumer group. The number of clients that a single EventMesh instance can support is limited by the number of consumers and the average number of clients in every consumer group. Each consumer has a private resource pool. In general, this resource pool includes but is not limited to a collection of threads, such as threads used to obtain messages and consumption, and some timing threads used to access the registry. When there are a limited number of consumers After being created on the EventMesh instance, a resource explosion will occur. The producer has simple logic, takes up less resources and can be ignored. like this, when several consumers are created, the JVM will not have enough threads, and the memory resources will run stably  Scene P1 and Scene P2 show the number of clients that a single EventMesh instance can support in two cases (on average, a single consumer group has more clients and fewer clients).  Obviously, in terms of quantity, scenario 1 is better In scene 2. ### Describe the solution you'd like Global consumer, a single EventMesh instance has one and only one singleton Consumer & Producer, this singleton Consumer&Producer is responsible for all clients connected to the EventMesh to send and receive events, if a single EventMesh instance only has one global consumer, include three parts 1. manage meta-data about client-group mapping ~ meta-data table like example ~ sync meta-data with broadcast  2. local ack manage ~ The consumption progress of EventMesh is managed separately from the consumption progress of the actual consumer group  ### Describe alternatives you've considered -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
