Issue Task Resolved

#109601Resolving legacy SiteSettings slows down massively with many sites and settings

Julian Hofmann 04/16/26, 12:17 updated 10/22/26, 07:55

Description

We have an instance with around 200 sites/root pages, each with approximately 50 settings.
After clearing the caches, the first request took around 100 seconds.

When investigating the cause, it soon became apparent that around 70% of the time was spent on `ArrayUtility::getValueByPath()`, which is primarily called via `SiteSettingsProvider::getProvidedSettings()`.

Ultimately, it turned out that the handling of (potential) legacy settings introduced with ‘#106894 – Site settings.yaml is now stored as a map’ leads – in the case of many sites with many settings – to these massive performance losses. This results in a veritable array massacre.

Possible solution

  • Migrate all settings to map notation.
  • Remove the resolving of legacy SiteSettings in `SiteSettingsProvider::getProvidedSettings()`
In this specific case, an uncached request took:
  • 106s with legacy handling
  • 4s without legacy handling

Reviews 2

Files 1

History 510

  1. Julian Hofmann changed subject Resoling legacy SiteSettings slows down massively with many sites and settings Resolving legacy SiteSettings slows down massively with many sites and settings <span data-processor="relativetime" data-value="2026-04-16T14:00:49+00:00" > 04/16/26, 14:00 </span>

  2. Wolfgang Klinger commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-22T07:55:13+00:00" > 10/22/26, 07:55 </span>

    Applied in changeset commit:e422e1e7cb684b4a274a904b3136a1feed13b8c6.