Problem/Motivation
Drupal 8 now has 99% coverage for cache tags:
- ~99% of things that can be changed and affect the rendered output have cache tags
- ~99% of those have test coverage, see e.g.
EntityCacheTagsTestBaseand subclasses
Those cache tags are present in the X-Drupal-Cache-Tags header, which the page cache uses as the cache tags for its cache items. This means that already, whenever something changes, the affected cached pages in the page cache are invalidated.
The benefits are enormous:
- all Drupal 8 sites will be fast by default for anonymous traffic
- "fast by default": roughly 10 milliseconds per page load instead of 100–300 — so ten to thirty times faster!
- all simpler sites (think: Drupal developers' blogs, local sports club, small businesses) will be plenty fast, even on cheap hosting — thus resulting in greater satisfaction with D8
- in the typical, poorly done benchmarks, Drupal 8 will leapfrog Drupal 7, and all of its competitors
- … and still see results show up instantaneously!
Proposed resolution
Enable page caching by default!
Remaining tasks
None.
User interface changes
None.
API changes
None.
Original report by @sun
I don't see nor understand why we decrease performance by default.
I'm sure this is one of the points that adds negative karma to Drupal.
Even the interface says: "Normal (recommended)"
So let's just enable page caching by default and make anonymous users happier.