github.com/pingcap/tidb/context.Context.GetSessionVars
third-partyThe 938th most-called third-party method by production calls. Called 817 times across 1 modules; 705 of those run outside tests and generated code.
All of github.com/pingcap/tidb/context → Docs on pkg.go.dev ↗
- prod calls
- 705
- non-test, non-generated
- all calls
- 817
- total callsites
- modules
- 1
- distinct callers
- in loop
- 5%
- of prod calls
- in tests
- 14%
- 112 calls
- resolved
- 0%
- 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 →
- Interface method100%Called through an interface. The runtime target may differ.
who calls this
Notable callers
Production calls into Context.GetSessionVars from notable Go projects. Open one on the map to see what else it hammers.
- TiDB 705 100%
where it's called
Callsites in the wild
12 representative callsites of 817, prioritizing in-loop and non-test usage. We link to source, never display it.
-
pingcap/tidb @v1.0.9
in loop - in loop
- in loop
- in loop
- in loop
- in loop
-
pingcap/tidb @v1.0.9
in loop - in loop
-
pingcap/tidb @v1.0.9
in loop - in loop
- in loop
- in loop
top callers
The modules that reach for it
The modules that call Context.GetSessionVars most in this snapshot.
- github.com/pingcap/tidb817100%