github.com/VictoriaMetrics/VictoriaMetrics/lib/cgroup.AvailableCPUs
third-partyThe 6572nd most-called third-party function by production calls. Called 101 times across 2 modules; 90 of those run outside tests and generated code.
All of github.com/VictoriaMetrics/VictoriaMetrics/lib/cgroup → Docs on pkg.go.dev ↗
- prod calls
- 90
- non-test, non-generated
- all calls
- 101
- total callsites
- modules
- 2
- distinct callers
- in loop
- 0%
- of prod calls
- in tests
- 11%
- 11 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function45%A direct call to an exported package function, resolved by type.
- Package function (by syntax)55%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into AvailableCPUs from notable Go projects. Open one on the map to see what else it hammers.
- VictoriaMetrics 90 100%
where it's called
Callsites in the wild
12 representative callsites of 101, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop test
- in loop test
- in loop test
- in loop test
-
-
-
-
-
-
-
-
top callers
The modules that reach for it
The modules that call AvailableCPUs most in this snapshot.
- github.com/VictoriaMetrics/VictoriaLogs5655%
- github.com/VictoriaMetrics/VictoriaMetrics4545%