Optimize _domain_conf_load_primary

Created on 14 January 2011, almost 14 years ago

Updated 3 September 2024, 4 months ago

Two problems with this query --

1. variable_init uses SELECT * FROM variable, while this uses "name, value" -- causing query_cache to treat them independently.

2. variable_init has likely already generated and stored the variables in a static cache. In my case, my {variable} table is large (5.x -> 6.x upgrade site -- cleaned the table from 5000 to 3000 records, but still many in use) and has lots (megabytes) of data. We should leverage the cache that is already generated?

After cache_get/cache_set queries, variable queries are my next on-every-page highest.

📌 Task

Status

Closed: outdated

Version

2.0

Component

Code

Created by

jason.fisher

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 4 months ago →
🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
I'll close this issue due to inactivity for 14 years and even if I would move it to the next nearest core version which is 7, there is upcoming EOL of Drupal 7 in January 2025. While the project's version for Drupal 7 will surely keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. A big thanks around for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024