You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@kafka.apache.org by pengfei li <lp...@gmail.com> on 2015/05/13 18:09:43 UTC

the performance of producer[async] degraded seriously after full gc

Hi,
    Recently, we use kafka for message transport, And i found something
strange in produer.
    We use producer in async mode, and if i trigger a full gc by jmap
-histo:live, then the performance of producer degraded seriously.
    Then,I found there were a lot of scala.collection.immutable.Stream$Cons
in jvm heap(one order of magnitude higher than before full gc).
    Could anyone help me to find the answer?
    Thanks.