Closed
Description
A Google production service experienced a performance regression with the Go runtime's use of MADV_COLLAPSE
. We've narrowed down the issue to exactly that call. We suspect the issue is that MADV_COLLAPSE
can go into direct reclaim while we're holding the heap lock. We suspect this issue is more widely applicable.
For now, let's roll back uses of MADV_COLLAPSE
. We can revisit this in the future, but our current policy is almost certainly too aggressive given the costs.