I’ve been using Bubbles for a few months now and loving it but my editor speed is getting slower and slower over time. I understand that the live site speed base on the respective plan, but does the editor have the same restriction?
Sometimes my editor is so slow it’s almost unusable. We’re talking seconds between clicks.
Is this a common thing that we live with?
Any suggestion on how I can improve my editor speed?
my computer and internet connection are pretty fast so unlikely to be from my end.
My system is:
Ram 32GB
Threadripper 1950X 16-core 3.4GHZ
windows 10
Chrome Browser
SSD drive
internet is 80+ Bbps
about 9 plugins but only using a couple.
Ok, definitely not a PC problem lol. I use firefox because I have noticed that my browser crashes when using bubble on chrome. Maybe try another browser and see how that goes for you?
Do yo have a big app in a single page? I had the same problem and if this is the case you may have no choice other than break your app into separated pages.
@lockymadera Thanks, I am trying out Firefox, seems to be faster. Let give it a few days. @anwarsby yes it’s a bigish single app with data and calculations using the math.js plugin however while editing, I only edit 1 section at a time by hiding the other groups. Not sure if that makes a difference.
the thing is, sometimes it’s fast, sometimes it’s slow.
@hello.plannwin hiding most groups while editing won’t make any difference in my experience. The editor will be suddently much slower when browser’s memory reach a certain amount, in my case around 2.5gb (chrome).
I have the same issue and have found it started within the past couple weeks. I use both a 16" MacBook Pro fully spec’d as well as my desktop PC running an i7 with 32GB of RAM.
Sometimes doing things like clicking deploy to live will say “checking your app” for a solid 5 minutes before the window appears to deploy it. Have the same issue on both machines, using Chrome, as well as Safari sometimes on Mac. Deleting 2000 records takes forever as well. I wanted to delete that many yesterday but from the editor it wouldn’t work at all, it would run for 10 minutes then say Bubble is out of memory try again later, so I’d refresh to see that 1800 records remained, so 10 minutes to just delete 200 of them. I tried via workflow using a button but that would do the same thing, runs awhile then pops up a message that the server is out of memory and my task has been cancelled.
Mac runs it better than my PC does but lately it absolutely has been way slower. Click an input box in the editor and it doesn’t register I clicked for 1-2 seconds and so on.
I wish we could warn people who are building a big page. I talk about this in many posts, but it will always be better to have everything on the same page, and light in the editor.
Sluggish editor on SPA’s is an ongoing problem for Bubble unfortunately. I have a Mac Pro with 128 GB RAM, and large pages still become frustratingly unresponsive, so don’t go out and invest in a monstrous amount of RAM to solve this this, just saying…
Some tips that may help you:
In my experience, keeping the editor open in more than one window at a time can drastically slow it down and lead to frequent crashes (even if it’s not the same page open). The same goes for working with collaborators.
Firefox handles it a bit better than Chrome (but page zoom is not support in FF)
Moving parts of the page into reusable elements can speed things up significantly, but is only recommended if you’re well familiar with the pros and cons of using reusables
A more high-end plan will not provide any major improvement - this is a bubble/browser issue, not a server issue
Trying to develop good habits in keeping the page as lightweight as possible (remove unneeded plugins, fonts, elements, header scripts, conditions, combine workflows into custom workflows, etc) is of course good advice in general
Closing Chrome completely and starting over improves it for a while. Long enough to be worth it
There’s no magic wand to solve this at the moment unfortunately. Maybe the upcoming UX upgrade improves the situation, we don’t know for now.
EDIT: for people mentioning that deleting records in the db etc, can take a long time or timeout, this is not the kind of problems I’m describing above. In that case, the problems has two solutions: change the workflow to space out the operation over time, or upgrade your plan. I’m talking specifically about the problem of the editor itself becoming slow on big pages, not about database operations.
Also have an iMac with 32GB Ram and can not use Chrome it just locks up and Firefox does overtime. I have fond Safari to be the best performing and I also like that Safari lets me know when the amount of resources being consumed is causing perfomance issues and I then know to close down a few tabs…
Welcome to my Hell…
Where have all you been hiding all this time… This has to be one of the big frustrations…
I had to adandon 8GB and i5 for a 32GB Mac (note Safari browser still complains …) and Google chrome on the MAC eventually grinds to a halt with continuous editing on Bubble.
I have been advised by bubble support to refresh frequently and clear it out or memory every so often,
However, in my frank opinion, this is a cop out by Bubble.
Sort out your memory management and don’t disenfranchise users on regular priced computers.
Yes Also, the app size was mentioned as another retarding factor… and yes this is unfortunately where bubble MVP meets its limits.
To be fair, the Bubble editor does seem to have to keep track of a lot of things, which given that you lose them on refresh, I assume means that it holds them in memory as opposed to in a database. I’m talking about all changes made in the session in particular but also your last copied workflow, element, element with workflow, expression, expression-field, condition, style etc; loaded fonts etc.
Maybe a gentle warning (please, not another popup) to say when the data held in memory is approaching critical levels (assuming it knows) and a way to jettison some of the load - on a first in first out basis?
Can’t help commenting here, as this kind of response is basically the go-to assessment on any issue discussed long enough, especially from newer users. As frustration reaches a certain point, people seem to forget that there are hundreds of other issues that are just as important to other users than yourself. Disenfranchising users on regular priced computer is hardly true. As I’ve mentioned, I’m on a computer that’s frankly preposterously expensive that other parts of my work happened to provide me with, and if 128 GB can’t cover the memory need of a web application, no amount of RAM would. I also have a MacBook with 8GB RAM, and honestly, when I’m using Bubble on an external monitor, I forget which one is plugged in. So I can assure you this issue is perfectly socially democratic.
Rebuilding the Bubble editor to handle bigger apps is probably one of the biggest asks you can give the Bubble team. It would mean drastically reducing updates in other areas where people expect it. It would mean reducing work on the front-end performance. It’s all a matter of priorities, and many users, myself included, would not agree that this is the most pressing issue they should address. Maybe they’re working on it in the coming UX update, maybe not. My guess is we’ll see small improvements spaced out over a few years, slowly fading out the discussions that this was ever a problem.
I feel your frustration and I’m not mocking you. Maybe your comment wasn’t meant as harshly as I interpret it, and you happened to become the target of this built-up rant of mine.
But there is this weird sense of entitlement that I keep seeing over and over on this board that Bubble somehow owes them something, or should shape up and move all their resources to this one issue that’s bothering them. And it usually ends with a dramatic statement like “this is the end of the run for me Bubble, it was fun while it lasted”.
