Problem/Motivation
Follow-up to #2342045: Standard views base fields need to use same rendering as Field UI fields, for formatting, access checking, and translation consistency.
Blocking critical #2381277: [PP-1] Make Views use render caching
Will help with performance.
https://www.drupal.org/project/views_row_cache exists for 7.x contrib.
Caching views rows would mean we'd get similar behaviour on cache misses to full entity rendering:
1. Cache hit - single cache get from views output cache
2. Entity list tag is invalidated
3. a. Both the row for that entity, and the views output cache misses
b. However, now all the other rows rendered by the view are a cache hit
Proposed resolution
Remaining tasks
Things to look at:
- how much extra work on a cold cache (i.e. a view with 50 items per page will be 50 additional cache sets)
- can we use multiple get on the rows to avoid 49 individual cache gets? Are 49 individual cache gets + 1 cache set worse than just doing the rendering?
Once we have a resolution, decide if we need a change record.