Excessive memory usage when Traefik processes thousands of regex-based routing rules
The goal is to understand whether Traefik’s internal routing tree immediately releases memory when a configuration provider removes a regex‑based route, or if the nodes persist until the Go garbage collector reclaims them. In environments with high‑frequency updates—such as thousands of regex rules being added and removed rapidly—there is uncertainty about w
traefikproxy