I've been looking into using Drupal with millions of nodes. One problem is that the admin/settings/search page is very slow. This tends to cause CPU quota errors on shared hosting.
The query causing the problem is this one:
SELECT COUNT(*) FROM node n LEFT JOIN search_dataset d ON d.type = 'node' AND d.sid = n.nid WHERE n.status = 1 AND (d.sid IS NULL OR d.reindex <> 0)
which has roughly the same problems as the query in node_update_index(), and could be fixed with a similar approach.
When a node is added to Drupal, add an entry to the search dataset so that we can avoid this join and the NULL thing and just look for d.reindex <> 0 to find the status.
Also may need to set the d.reindex value to something that will trigger new nodes to be indexed first in NodeSearch::updateIndex, like a value of 1, and the code in that function can also be simplified so it does not have to consider NULL entries.
Make a patch.
Faster cron and search status page loading.
Not really.
Needs work
11.0 🔥
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 doesn't seem to be novice type work here right now.
This issue is also triggered when visiting normal /admin/config page and causes timeout on sites with lots of nodes. See
https://www.drupal.org/project/drupal/issues/3336621#comment-16067058
🐛
Slow admin/config page load
Needs work