5 ms·
Varnish does handle the mass of logged out cached requests. However, because they were having such a high amount of page edits per second the cache in Varnish
by Washuu 10y ago
Varnish does handle the mass of logged out cached requests. However, because they were having such a high amount of page edits per second the cache in Varnish would only by valid for about a second. Then a flood of logged out users hit the servers at the same requesting the uncached page to be rendered. The PoolCounter extensions keeps the web servers under control and by throttling requests for page rendering.
- danielrhodes 10y agoCorrect me if I am wrong, but I thought Varnish has support for limiting concurrent backend fetches to the same resource.
- brianwawok 10y agoAcross a cluster of varnishes? I think that limit is per varnish.
- danielrhodes 10y agoNo, definitely not across a cluster (although that would be quite nifty). Even on a single node that would reduce the thundering herd effect substantially.
- chris_wot 10y agoMaybe that's a new feature request!
- seanp2k2 10y agoWhy not just set the min TTL to a few minutes, or even a minute, for anonymous users? Is there enough usefulness in ~seconds of delay on article edits vs minutes to warrant a much more complex design?