- Issue created by @e0ipso
- 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺
Per @pameeela:
Just FYI, we are just one day away from a commit freeze for the RC release of Drupal CMS on Monday, and from there, we won't be able to add any major new features until after version 1 is released on Jan 15.
So I'm sad this might need to wait.
- 🇬🇧United Kingdom catch
Very low traffic sites won't have cron configured, and will rely on automated cron which happens end of web requests. While it should more reliably happen after the request is sent to the browser after 🐛 Post-response task running (destructable services) are actually blocking; add test coverage and warn for common misconfiguration Fixed , that's not guaranteed on all environments, so if prewarming is happening during cron, which is happening during web requests, it could be counter productive.
I would personally prefer to see effort on 📌 Add a cache prewarm API and use it to distribute cache rebuids after cache clears / during stampedes Needs work and 🌱 Adopt the Revolt event loop for async task orchestration Active which could significantly speed up cold cache requests in their own right. This would also make the prewarming itself more efficient if we still wanted to do that.