entity_info:en
views:display
views:sort
views:filter
views:area
views:pager
views:query
views:join
views:style
views:row
views:cache
typed_data:types:en
views:exposed_form
field_types:en
field_formatter_types:en
filter_plugins:en
block_plugins:en
That's the list of cache requests of various plugin types that I get right now on the front page that just displays some nodes.
We should consider to use a cache collector to for example group all views plugin types together into a single cache. It will always request all of those when any is requested.
The others might be a bit more complicated, but grouping all entity/field/data caches together probably also makes sense, those are needed together too. entity info used to get big due to bundles and view modes, that is no longer in there, luckily.
Not sure about the API changes/additions, maybe cache collector needs to implement cachebackendinterface to work transparently and also support tags and so on...? Tagging with addition for now...
Comment | File | Size | Author |
---|---|---|---|
#3 | test.patch | 4.34 KB | dawehner |
Comments
Comment #1
yched CreditAttribution: yched commentedfield types + widgets + formatters were also one single cache entry in D7.
Although, well, on most pages (that don't display form), the widget info is actually not needed.
Comment #2
catch#2114319: Lots of cache requests from plugin discovery was duplicate, and major.
Comment #3
dawehnerWhile just trying to write a prototype (which isnot even a cache collector) I wondered several things:
Comment #4
catchPostponing on #2228261: Add a local, PhpStorage-based cache backend and #2228291: Move all plugin and other discovery data into a cache_discovery bin.
Comment #5
sunComment #6
catchMoving this to duplicate. If the local cache issue turns out to be a dead end, we can re-open this.