bryancall commented on issue #9124: URL: https://github.com/apache/trafficserver/issues/9124#issuecomment-4827450326
The cache directory sync path has been reworked since this was filed. In [PR #12639](https://github.com/apache/trafficserver/pull/12639) (first released in 10.2.0) the sync continuation was moved off the ET_NET threads onto ET_TASK threads, and a new setting, proxy.config.cache.dir.sync_parallel_tasks, was added (a value of -1 means one sync task per drive). That lets the stripes of a single drive be synced in parallel, which is the same effect you obtained manually by splitting one NVMe into five volumes. The throttle constants this report pointed at are now runtime tunables as well (proxy.config.cache.dir.sync_max_write and proxy.config.cache.dir.sync_delay) instead of the old compile-time SYNC_MAX_WRITE and SYNC_DELAY values. Since the contention on the ET_NET path and the single-task-per-drive limitation that drove the read-time spikes have both been addressed, I am closing this. Please reopen with details if you still see read-latency spikes during directory sync on a current release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
