out all running goroutines ● Before the unit test runs, remembers all running goroutines ● After the unit test is finished, if there are any new goroutines, that are leaked goroutines func TestT(t *testing

it block all the callers ● The scheduler treat them equally Analysis ● Under heavy workload, goroutines get longer to be scheduled ● The runtime scheduling does not consider priority ● CPU dense workload Observation： A query is blocked by GC sweep Investigation ● The garbage collector can stop individual goroutines, even without STW ○ eg. A goroutine that needs to allocate memory right after a GC cycle is required

lines of Go code and 94 contributors. Goroutine • Starting a goroutine is easy and cheap. • Goroutines come with built-in primitives to communicate safely between themselves (channels). • Very easy

The time for which TiKV nodes and TiCDC nodes have been running • Goroutine count: The number of goroutines of a TiCDC node • Open FD count: The number of file handles opened by TiCDC nodes • Ownership: Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between sync-diff-inspector and upstream/downstream Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between upstream and downstream databases

run immediately after a Region is initialized #2235 * Optimize workerpool to reduce the number of goroutines under high concur- rency #2201 – Dumpling * Support always splitting TiDB v3.x tables through The time for which TiKV nodes and TiCDC nodes have been running • Goroutine count: The number of goroutines of a TiCDC node • Open FD count: The number of file handles opened by TiCDC nodes • Ownership: each chunk. ### Uses "chunk-size" to set the size of a chunk. chunk-size = 1000 ### The number of goroutines created to check data check-thread-count = 4 ### The proportion of sampling check. If you set

The time for which TiKV nodes and TiCDC nodes have been running • Goroutine count: The number of goroutines of a TiCDC node • Open FD count: The number of file handles opened by TiCDC nodes • Ownership: each chunk. ### Uses "chunk-size" to set the size of a chunk. chunk-size = 1000 ### The number of goroutines created to check data check-thread-count = 4 ### The proportion of sampling check. If you set Uses "chunk-size" to set the size of a �→ chunk. 1201 chunk-size = 1000 ### The number of goroutines created to check data check-thread-count = 4 ### The proportion of sampling check. If you set

The time for which TiKV nodes and TiCDC nodes have been running • Goroutine count: The number of goroutines of a TiCDC node • Open FD count: The number of file handles opened by TiCDC nodes • Ownership: Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between sync-diff-inspector and upstream/downstream Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between upstream and downstream databases

The time for which TiKV nodes and TiCDC nodes have been running • Goroutine count: The number of goroutines of a TiCDC node • Open FD count: The number of file handles opened by TiCDC nodes • Ownership: Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between sync-diff-inspector and upstream/downstream Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between upstream and downstream databases

per TiCDC node. • Memory usage: the memory usage per TiCDC node. • Goroutine count: the number of goroutines per TiCDC node. 11.1.5.2 Key metrics for TiCDC data replication 1357 11.1.5.2.1 TiCDC overall The time for which TiKV nodes and TiCDC nodes have been running • Goroutine count: The number of goroutines of a TiCDC node • Open FD count: The number of file handles opened by TiCDC nodes • Ownership: Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between sync-diff-inspector and upstream/downstream

per TiCDC node. • Memory usage: the memory usage per TiCDC node. • Goroutine count: the number of goroutines per TiCDC node. 11.1.5.2 Key metrics for TiCDC data replication 1343 11.1.5.2.1 TiCDC overall The time for which TiKV nodes and TiCDC nodes have been running • Goroutine count: The number of goroutines of a TiCDC node • Open FD count: The number of file handles opened by TiCDC nodes • Ownership: Configuration. ########################### Global config ######################### ### The number of goroutines created to check data. The number of �→ connections between sync-diff-inspector and upstream/downstream