Perhaps this is obvious, but suddenly heavy garbage *collection* operations
suggest heavy garbage *creation* operations; that new code or structure is
allocating and discarding more than the old. You've gone from single to
multiple caches, so my thoughts go to: is data cached redundantly? (is the
the memory yourself, and typically requires a lot more error prone code to do so.-Original Message-
From: Joseph Wang
Sent: Jun 4, 2019 2:16 AM
To: golang-nuts
Subject: [go-nuts] How can I debug high garbage collection rate cause high CPU usage issue in golang
Hello everyoneI just have
Hello everyone
I just have a question about my golang code debugging. It's not specific
code question. But I never met this issue before.
The problem is like this. I replaced our back-end system's cache from
single node cache to groupcache that is a kind mem cache. Then I met high
memory
