On admin user the frontpage has a couple of entity queries: (~100ms is the entire request in that example.)
which are not necessarily cheap to execute.
One part of the chain of functions is
which you can see, is not really cheap, but if you think about it, could be actually cached. The table mapping of an entity type should really not change between requests.
Maybe think about better ideas how to optimize it.
Needs work
9.5
It affects performance. It is often combined with the Needs profiling tag.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The reroll in #27 is missing hunks of the patch that actually add the caching. #6 seems to be the last version of the patch with those changes.
#27 is an incomplete patch, any further work here needs to start with a re-roll of #6 and ignore all the patches in-between.