There is a discussion going on about this question on the golang-nuts mailing list in case anyone is interested: https://groups.google.com/d/msg/golang-nuts/Ahk-HunIqgs/3JTlBKRcCQAJ
On Mon, Nov 28, 2016 at 7:59 AM, Devanand Reddy <[email protected]> wrote: > Hi there, > > We are using protocol buffers extensively in our application. We have a > suspect that over the time, due to excessive marshaling/un-marshaling > these two operations are causing heap fragmentation. One factor I am > looking at, to come to this conclusion is HeapIdle. In my tests, though > HeapInUse is coming back to my expectation, HeapIdle is staying there > forever. On another note, our protobuff operations consume any where > between 700-900mb, given the size of the data we are trying to serialize. > I am attaching a few graphs here. > > Please advise whether this is a sign for concern. > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
