If i have 10,000 data, bubble is too slow, I noticed a big issue

Hi! It’s been a long time, and I’m not sure if you still need this, but you won’t be able to handle large data with instant display in Bubble the way you want (without pagination, I believe).

I recommend starting to use your own MySQL or PostgreSQL server in your application… I’ve been studying MySQL, and it has worked well for most of my use cases.

I analyzed some data I obtained:

  1. I was able to iterate through a list of 10 million customer records and filter by customer name; it took 0.086 seconds using the INDEX function in MySQL.
  2. I managed to display 10,000 data entries in a repeating group, without pagination, in 0.692 seconds.
  3. I managed to display 50,000 data entries in a repeating group, without pagination, in 1.753 seconds.
  4. I managed to add 1,000,000 rows to the database in a single operation in less than 10 seconds.

It’s obvious that you won’t display 50,000 data entries without pagination on your site because it would be like crashing all your users’ devices, but this is just to demonstrate the power I achieved… by paying for a hosting service costing $5.20 per month.

MySQL has advanced filters and many amazing commands, just like PostgreSQL (which Bubble itself uses, I think)…

Since you can’t export code in Bubble, giving your client the freedom to use phpMyAdmin and allowing them to have full control over the data that enters and exits significantly boosts your credibility.

PS: Don’t use Bubble’s SQL Connector if you want speed. I tested it, and it’s much better to create a custom plugin using a Node.js module:

{
    "dependencies": {
        "mysql": "latest"
    }
}

If you don’t want to pay WUs for each MySQL database action, then try creating a client-side plugin instead of a server-side one.

Then what’s the point of using Bubble? Many other front-end builders that are faster than Bubble. Bubble’s value is in its DB and front end integration. When could you possibly need to download 50,000 objects to display to the client?

This would have warmup time of a couple of seconds for the first request that takes place every few minutes which would be way slower than Bubble’s search

Bubble is more complex than just being a front-end builder. Using an external database saves money and increases speed depending on your use case, and I think this is the main focus for many people. Complex applications can cost several dollars just in database logistics, and having that cost tied up in Bubble is a hassle. An external database allows you to display your app’s data anywhere and gives you much more control (though Bubble’s internal database also allows this, but again, it would require requests to their servers, which would cost WUs).

It’s also perfect if you want to build an app in Flutterflow from your Bubble site. You wouldn’t need to pay for Flutterflow’s PRO plan plus the database and operational costs of Bubble, which would basically serve as a hidden backend for FF

Yes, that is one of the main issues. The first request usually takes longer in my tests. But if you have a base of daily active users established, it will almost be imperceptible