- 🇬🇧United Kingdom catch
There has been lots of profiling of core since and this hasn't shown up as a problem, closing out.
Updated: Comment #0
In #1862202-341: Objectify the language system → the following argument was raised:
[
PathProcessorLanguage] This looks like a lot of runtime overhead in the critical path?
Can we find a way to prepare this information ahead of time; e.g., in a new Container CompilerPass? [...]
That said, the dependent code in this class is manually probing whether $processors[$type] is set already, which could be inlined (once) into the initProcessors() method.
[...]
Paths/URLs definitely depend on the current (sub-)request [think ESI], so any kind of static cache can very easily not be a given and not reliable/performant anymore.
TBD
TBD
TBD
Closed: outdated
11.0 🔥
language system
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
It affects performance. It is often combined with the Needs profiling tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There has been lots of profiling of core since and this hasn't shown up as a problem, closing out.