The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I am upgrading a site to the latest releases and (at least) one view-based finder seems to run 4-6 times slower than before. The content type in question has about 380 nodes.
After some digging I narrowed down the problem to the SQL generated to fetch the possible choices to expose in the form.
The latest version does not have a GROUP BY clause that would reduce the choices to read from 1675 to 347.
I reviewed the diff between the two Finder releases (6.14 and 6.27) and could not see why this should happen.
Attached are the SQL statements generated by the upgraded site and the production one.
Can someone shed some light on the matter?
Are the two SQL queries supposed to be so different and should I start looking elsewhere ?
Thanks a lot for your help
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | finder_resources.txt | 9.6 KB | savedario |
| finder_performance.txt | 3.16 KB | savedario |
Comments
Comment #1
savedario commentedJust in case it could be helpful, here's the exported Finder.
Comment #2
savedario commentedGiven that the update 6.17 > 6.27 did not include any database changes, I quickly replaced the Finder's new code with the old one and the issue above disappeared.
I updated the status of this issue accordingly.
Comment #3
verta commentedTweak to issue title for SEO and add tag, +following.
Comment #4
dragon658 commentedI also have such problems.
Before last update of views module my finder auto-complete worked fine, but now it takes more than 10 seconds to load.
Comment #5
danielb commentedDrupal 6 is no longer supported.