Bubble.io Best Practices for (Correct) Workload Optimization

[@paulpickett4522]

I've heard "contianed list fields" referred to in this and a previous CNCA video on Workload Optimization. What is that referring to exactly? And thanks so much for making resources like this available on KZbin.

[@tastebluds]

I’ve been changing all my iterative workflows to Make changes to a list using a block size of 100. In tests it showed a huge reduction in WU’s. Is this not right?

[@riscc94]

has it never timed out? how long are you scheduling them apart?

[@paulpickett4522]

Unless I'm mistaken, that seems to mesh well with what she said. The biggest concern with making changes to a list is it timing out. Using a recursive workflow to avoid that weakness, but using it to launch a series of "make changes to a list" workflows sounds like a great plan. I think @riscc94 has a point that so long as nothing times out it's great, and if something did time out you would just lengthen how long between when the recursive workflow fires off another list of 100 items for the workflow so that you don't overload some capacity somewhere - (I'm not sure how they throttle moment-by-moment capacity, especially with recent changes, but yeah, I would think that's the only thing that could cause a problem with your approach). And, btw, CNCA is typically a fan of whatever works =) Especially if you know the potential pitfalls and guard against them.

[@camilla3254]

Thanks ❤

[@coachingnocodeapps]

You're welcome 😊

[@falecomguilhermelima]

Unfortunately all that will be ruined if your user create a bot to press F5 in a page with heavy processing workflows.

[@coachingnocodeapps]

It's tough because there will always be a worst case scenario, no matter what you're doing, app development or otherwise. Generally you have to weigh your options and move forward with some potential worst case scenarios present. You can't truly avoid them all unless you simply don't build an app, launch a business, etc.

[@paulpickett4522]

It would take some precious resources to implement it for all users all of the time, but If you want to guard against that particular case, you could put a counter on the user or a connected record that counts up each time they visit a page and reset it every # of days, and if the counter ever gets above a certain value, fire a message off to yourself and/or have an action that gives them a captcha to solve to continue acting in your app...? But you certainly can't plan for everything. (e.g. every vehicle you pass on the road you choose to trust not to swerve into you. You have to accept this or you can't drive.) But you could have plans like the above written down in a list of contingency plans to look up and use if you think you're receiving that kind of ill-natured user behavior...if that would give you some peace of mind.