Dan Ramich f39ca994bd Don't start goroutine for noMetrics ...

Problem:
When calling newQueue metrics can be of type noMetrics when just calling
New. When doing this a new goroutine is created to update the metrics
but in this case there are no metrics so it's just creating goroutines
that don't do anything but consume resources.

Solution:
If the incoming metrics is of type noMetrics, don't start the goroutine

Kubernetes-commit: de021396f81ff438899297a6f464c70113b58475

2020-09-15 16:21:48 -06:00

..

default_rate_limiters_test.go

Revert "Implement ItemBucketRateLimiter"

2020-03-05 14:35:19 +01:00

default_rate_limiters.go

Revert "Implement ItemBucketRateLimiter"

2020-03-05 14:35:19 +01:00

delaying_queue_test.go

…

delaying_queue.go

Export new constructor for DelayingQueue

2020-03-23 12:15:29 +08:00

doc.go

…

main_test.go

…

metrics_test.go

test(workqueue): deflake TestMetrics

2020-09-05 18:50:45 +08:00

metrics.go

…

parallelizer_test.go

Use sqrt(n) chunk size in pod affinity and core scheduler

2020-03-16 14:12:11 -04:00

parallelizer.go

Add chunk size option to ParallelizeUntil

2020-03-11 17:13:55 -04:00

queue_test.go

…

queue.go

Don't start goroutine for noMetrics

2020-09-15 16:21:48 -06:00

rate_limiting_queue_test.go

…

rate_limiting_queue.go

…