Closed (outdated)
Project:
Domain
Version:
7.x-3.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 May 2016 at 09:45 UTC
Updated:
2 May 2025 at 12:17 UTC
Jump to comment: Most recent
Comments
Comment #2
agentrickardI think this is now a duplicate of #2695425: CRITICAL performance regression/issue with non-DB cache back-end..
Comment #3
ndobromirov commentedWe will have to validate it, but as far as I recall, they should not be related.
As the #2695425: CRITICAL performance regression/issue with non-DB cache back-end. is responsible for extraction of the default configurations for all domains, where this is for extracting the ones for the current. The data source is different and it happens on every request, always. The process was, if I recall correctly, load defaults, overwrite with custom ones for the domain cache everything in a static.
Will check when some more time is available.
Comment #4
agentrickardThanks!
Comment #5
ndobromirov commentedAs the other issue is fixed and committed now, this is open for development.
Currently open tasks here are:
1. Have the patch that adds the persistent cache layer. It should be part of the revere diff from this.
2. Research and see the configurations initialization flow and why the global conf from settings.php is lost in mid-bootstrap.
3 Patch etc.
4. Profiling the end result.
Comment #6
bluegeek9 commentedDrupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade.