Everything from

manual.bubble.io

2 resources from manual.bubble.io we point founders to, and the questions each answers.

📄 Article
✓ Link checked Free Intermediate

Why we picked it This is Bubble's own guide, and it names the exact levers that decide whether a search stays fast as your data grows: put constraints on the search itself instead of reaching for :filtered, keep sorts and filters at the database level, and watch out for searches nested inside repeating group cells. It is written against how Bubble actually queries data, so the advice maps directly to the slowdown you are seeing, not to generic web performance. Treat it as your first checklist before assuming you need to rebuild anything.

Performance and scaling

From manual.bubble.io by Bubble

  • Filters shown in the search palette run on the database and are fast; :filtered runs in the browser after the data loads and gets slow past a few thousand records, so move that logic into search constraints.
  • A search placed inside a repeating group cell runs once per row, which multiplies your query count; pull it out or restructure the data so one search feeds the whole list.
  • Order constraints from most to least restrictive and prefer exact matches over 'contains' so Bubble can eliminate the bulk of records early.
Open manual.bubble.io
🛠️ Tool
✓ Link checked Free Intermediate

Why we picked it This is Bubble's reference page on how searches actually execute, and it is the highest-leverage read for your problem because it explains that Bubble indexes your data automatically once the volume is large enough, and that privacy rules keep unmatched data from ever leaving the server. Understanding both means you can set your database up so the engine does the filtering for you instead of shipping thousands of rows to the browser first. Keep it open as a checklist while you audit each slow search in your app.

Searches (Optimization checklist)

From manual.bubble.io by Bubble

  • Bubble adds database indexes automatically for common query patterns once your dataset is big enough, and it does not cost extra workload, so structuring searches around real constraints lets that indexing kick in.
  • Privacy rules are not just security: fields a user cannot access never leave the server, which cuts the data returned to the browser and the workload that comes with it.
  • Text matching only indexes the first 256 characters, so very long text fields are a poor thing to search on when speed matters.
Open manual.bubble.io