Poor performance on searches with many results

[huntertur]

Capturing a discussion from 2025-01-01 in the developer chatroom.

When using a search query that returns many results (such as fox), the Next and Back buttons display a count of how many submissions there are to go. This count is capped to 10,000. For searches that return this many results, Weasyl will spend 260+ ms just in the query for these Next/Back counts, measured via ?query_debug, before the search results page is served to the user.

Suggested improvements from discussion:

• Asynchronously get these counts using fetch.
  • Possibly use Intersection Observer to do this lazily.
• Estimate the counts of how many submissions are left.
  • Exact count up to 100
  • TABLESAMPLE SYSTEM (10) on the content table up to 1,000
  • TABLESAMPLE SYSTEM (1) on the content table up to 10,000