- Issue created by @catch
Found via 📌 ContentTranslationHooks::viewsDataAlter() could multiple load config entities Active which I'll postpone on this issue.
That issue was in turn found by 📌 Add database and cache assertions to OpenTelemetryFrontPagePerformanceTest and OpenTelemetryNodePagePerformanceTest Active .
ContentTranslation module referencese a config entity for each possible entity/bundle combination on the system, however, these aren't guaranteed to be in the database. Whether translation is enabled for a bundle can be checked multiple times per request, so this can mean an attempt to load the entity/bundle from the system multiple times.
We can statically cache not found entities in the same static cache we use for found entities (using different keys), this should allow us to transparently avoid trying to load those entities multiple times.
Active
11.0 🔥
entity system
It affects performance. It is often combined with the Needs profiling tag.