3 Commits

Author	SHA1	Message	Date
Nikolay	e383b62f59	lib/timerpool: remove misleading panic ... After golang 1.23 it's safe to ignore timer.Reset True value. According to the spec: For a chan-based timer created with NewTimer, as of Go 1.23, any receive from t.C after Reset has returned is guaranteed not to receive a time value corresponding to the previous timer settings; If the program has not received from t.C already and the timer is running, Reset is guaranteed to return true. Before Go 1.23, the only safe way to use Reset was to call [Timer.Stop] and explicitly drain the timer first. Golang 1.23 changed timer implementation from sync and async. And it made possible that chan send and timer.Stop could happen in the same time. Fixes https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9721	2026-02-25 19:45:12 +01:00
Andrii Chubatiuk	6167ce655e	lib/timerpool: removed unneeded code, unified package usage (#9735) ... ### Describe Your Changes after golang 1.23 it's enough just to stop timer, no need to drain a channel related issue https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9721, but this is not a fix for it ### Checklist The following checks are **mandatory**: - [ ] My change adheres to [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/victoriametrics/contributing/#pull-request-checklist). - [ ] My change adheres to [VictoriaMetrics development goals](https://docs.victoriametrics.com/victoriametrics/goals/).	2025-09-16 09:55:33 +02:00
Aliaksandr Valialkin	e307a4d92c	lib/timerpool: use timer pool in concurrency limiters ... This should reduce the number of memory allocations in highly loaded system	2019-05-28 17:20:10 +03:00