Problem/Motivation
Some Views may be rendered without any caching or with suboptimal cache settings, causing repeated heavy database queries and rendering work on every request, which negatively impacts performance under load.
Steps to reproduce
Proposed resolution
Add a new Performance FitCheck plugin ViewsCachingCheck that:
- Scans all Views and their displays to detect those with caching disabled or using default “no cache” settings for results and/or rendered output.
- Fails with
FitWeight::Mediumwhen Views with significant query/render cost have no caching configured, listing the affected Views so administrators can enable appropriate time-based or tag-based caching. - Provides a short help message recommending enabling Views result/output caching (and, where appropriate, Views Content Cache or similar) following Drupal’s performance best practices.
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork drupalfit-3558984
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
harivansh commentedComment #5
shubham.prakash commentedComment #6
shubham.prakash commentedComment #8
harivansh commentedComment #10
harivansh commented