Hi Kafka community,
   I like to surface a KIP idea, which is to separate publish request from
the subscribe request using different ports.

   The context: We have some workload with over 5000 subscribers, the
latency on publish latency can be as high as 3000 ms second. After
investigation, we found the reason is mainly because there are too many
connections on socketserver and the multiplexing slows down the publish
latency.

   The proposal is somewhat similar to KIP-291: Separating controller
connections and requests from the data plane

   I like to check with experts here whether this is a viable idea to
continue pursuing or not?

Thanks!
Ming

Reply via email to