I have about 120,000 backend workflows scheduled right now, that are being tackled one by one. Each workflow is about 3 WU and it just makes an API call, makes changes to thing, and creates a new thing.
I can monitor how fast these are being completed in the WU tab, and also in the service I’m making API calls to:
And, like clockwork, every 15 minutes, it ramps back up.
Ideas, anyone? Nothing in the manual about how scheduled backend workflows are processed - I always believed they’d just run as fast as possible (and presumably at a consistent rate per second until all of them are complete).
I started mass deleting data in a couple data types in my database while still on the grandfathered plan. First one I started with was 52k records and of course it’s painfully slow to delete and figured it was a good time to just swap to WU since they claim it’s 1000x faster and not capacity limited and the “backend workflow on a list” speed update only applied to the WU plan.
I upgraded and expected it to be a breeze, unfortunately after 2 hrs of messing with it, trying bulk workflow in bubble backend, backend workflow on a list, and “delete list of things” as well as a parallel model since on WU plan you can run things in parallel in backend.
After the 2 hours I managed to get 7k records deleted…
Can anyone confirm the new WU plan is even faster, I won’t say it’s slower but to claim a speed increase at all after this experience seems crazy
*the backend workflow was simply 1 delete action with a “post” param passed.
My experience is similar. Overall much faster than legacy, but the throttling is at inconsistent intervals and for different (seemingly random) periods of time
It’s consistently and precisely 15 minute intervals for me (I bet 15 minutes is hard coded in Bubble’s system somewhere because it really is like clockwork). I thought it’d be like the red line, a consistent pace even if it’s slower but nope.
From this announcement. Curious if this is similar to everyone’s current experiences.
There is still some form of throttling it was from a related announcement. I remember because I commented on that point. Since one of the major selling points of WU was to remove any form of capacity based limit.
This is inline with experience from the past where you could setup a recursive flow, close your device and expect it to run all night at the same speed, but see a considerable drop. Strange Bubble would not have fixed that issue prior to pushing everybody onto the WU pricing structure. Seems like they were not ready for the switch.
