Be Aware: Looking at Your Data Tab Uses Your Plan's CPU

samnichols · 2022-09-19T04:08:58.567Z

This is something I wasn’t aware of until this evening, but apparently when you use the Data tab in the Bubble Editor, it can be quite costly in terms of CPU. While troubleshooting a small issue with one of our features, I needed to see a list of things created by a specific user.

I looked at App Data, added a filter for this specific thing that was “Created by = [user]”, and doing just that simple filter spiked our CPU to 40%. You’ll see this labelled as “Data panel search” in your Capacity Logs.

Screen Shot 2022-09-18 at 11.03.17 PM1454×676 73.1 KB

Good to note if you (like me) didn’t know that simply looking at things in the Data tab can cause massive CPU spikes.

reger-alexander · 2022-09-19T07:42:26.985Z

Thanks for sharing, I always wondered if this was the case but never bothered to check

viquarahmed07 · 2022-09-19T08:31:35.743Z

Hi @samnichols
I never checked this thing.
It gives me strange results …

Screenshot 2022-09-19 at 10.28.35693×520 47.1 KB

Time to fix capacity issues
Thanks

samnichols · 2022-09-19T21:40:31.103Z

It’s not the greatest tool, but sometimes it helps to see if there’s a particular workflow or action that shouldn’t be using much CPU but is. It helped me catch a couple small actions that seemed simple but for some reason were spiking CPU.

Our app recently released the ability to create CSV reports from the DB using backend workflows, which are NOT efficient, so I try to keep an eye on CPU usage generally and tweak things where I can. I don’t want to upgrade before I absolutely have to, lol.

equibodyapp · 2022-09-19T22:04:08.053Z

Yeah I’m finding creating CSV files in the backend using way more capacity than I thought - did you find a more efficient way to do this?

viquarahmed07 · 2022-09-19T22:25:12.875Z

@samnichols

samnichols:

I try to keep an eye on CPU usage generally and tweak things where I can

I will keep that in mind

Thanks

cmarchan · 2022-09-20T12:04:58.857Z

Interesting! Thanks for sharing.