@josh and @emmanuel, on the heels of A fair and honest chat about Performance, I too am experiencing performance issues and I don’t think they should be an issue unless there were tens or hundreds of users on my app. Right now, it’s only me in the development server and I’m getting tons of “app too busy (1)” errors while testing one workflow sequence.
I realize that I may not be building my workflow as efficiently as possible, but I would expect my app to perform better than it is on a “Professional” plan – maybe I’m naive in thinking “Professional” is enough for what I’m buiding. The only process I’m doing at the moment is calling APIs to get emails from a User’s email provider and processing them into Bubble. I’m getting the User’s folder structure and 2 emails from each folder, then transforming images, relating attachments, and some other items. This somewhat simple use case has some complexity involved, but I wouldn’t think that my whole app would be unusable or have the workflow terminated with such a small set of actions happening.
I understand that I may need to upgrade as the app grows, but I’m having hard time imagining what level I’ll need, and cost involved, if I’m already experiencing issues with only 1 user and very little system interaction.
Bubble is amazing, but if I’m only able to build static sites, or sites with very little processing/transaction throughput, I may be better off hiring a development team to build the app on another stack --which I don’t want to do, but may be forced to based on cost and performance limitations.
So, are there any suggestions you could provide to help? I realize you’re a small team with a large base and a huge list of to-do’s now, but I hope that there’s some fix for these issues or insight into what I’m doing wrong – outside of “you’re a dummy Keith and need to upgrade to a Team or Production plan”.