Ben Kochie

It would help to take a pprof sample when it's using over 200MB of memory, this way we can more easily find the memory leak.

Strange. The pprof only shows 9.6MiB fo memory in use. I would probably eliminate the CPU limit. I have seen CPU limits in K8s cause bad performance stalling. But I...

One additional debugging option, get a dump of the goroutines with `http://localhost:9100/debug/pprof/goroutine?debug=1`. Normally it would be only a few, [like this](http://demo.cloudalchemy.org:9100/debug/pprof/goroutine?debug=1).

The goroutine link doesn't require pprof, just `curl`. It's just a big text dump, not svg.

Looks like it's getting stuck on netlink. This is used by the wifi collector, try running the node_exporter with `--no-collector.wifi` /cc @mdlayher 😁 ``` goroutine 17790 [chan receive, 501 minutes,...

@mdlayher Maybe we should file a new issue with a cleaned up summary.

@mdlayher Did we ever get the upstream issue solved for this?

The problem with limiting threads is it will cause the scrape to be slow and just defer the problem. Remember, these are not OS threads, these are goroutines. If you...

IIRC, @rtreffer found the explicit 50ms delay in the kernel code.

Thanks, I'm guessing this would be solved with `GOMAXPROCS=1` as well.