kevin-pan-skydio commented on issue #1423: URL: https://github.com/apache/pulsar-client-go/issues/1423#issuecomment-3326019406
@AlvaroStream thanks for the response. In our setup we have cgo zstd enabled for compression. We’re observing the following: - Go heap usage is quite low (~80 MB, measured via the pprof heap endpoint). - However, the Go process shows a much higher resident memory footprint (~800 MB). When the go process stops publishing messages, the resident memory is not freed and remains at steady state 800MB. When we start publishing again, the resident memory grows. This mismatch suggests that the extra memory is not being tracked by the Go runtime, and points toward allocations coming from the C side of zstd. That leads us to believe the elevated memory usage is due to the cgo zstd implementation, rather than a leak in the Go heap itself. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
