Bricks Version: 1.6.1
Browser: Chrome 108
ServerOS: Linux
OS: Windows PC
[Please describe in as much detail as possible how we can replicate this bug]
When I save a page it often takes a very long time, when that happens I see that the server throws a warning about server load being too high
So somehow the saving part of Bricks seems to use far too many resources
I have the same issue.
Bricks 1.6.1
Chrome Version 108.0.5359.125 (Official Build) (64-bit)
Hi Oliver,
Thanks so much for your report, and welcome to the forum Alexander!
Can you please give me some details about your hosting environment, your plugins, and if it happens every time, even on pages with only a few elements?
Best regards,
timmse
Hi timmse 
My hosting is Hostinger.
The only plugin I have installed is WPCodeBox to work with sass.
I asked friends who also have Bricks and they also complain about a similar problem.
Hosting environment: vps with openlitespeed
Bricks 1.6.2
Chrome Version 109.0.5414.75 (Official Build) (64-bit)
It happens pretty much every time I make changes to a page and then save.
Thanks
Happens to me when saving larger sites with a bunch of ACF fields. My whole managed Server (Germany Mittwald) is not available for as long as saving process lasts. All server side cronjobs (even on other projects located on the same server) stop working …
Also: working on two DIFFERENT websites, located on the same server is impossible during saving process.
Hi @OllieMackJo , @Sashik, @beziehungsweise !
Please send us temporary wp-admin, FTP access, and a link to this thread to help@bricksbuilder.io.
If you can provide us with a debug.log file containing the error, it’d be super helpful in debugging the issue.
Best regards,
timmse
Hi @timmse,
I guess it doesn’t make sense to send login data NOW, for this reason:
I have been experiencing that when coming back later and tweaking things on such long dynamic templates, saving works fast as usual. So I guess the same will happen to you when you do some tests now. This is reproducible across several templates and across several sites …
It seems that this saving-lag only did show up (at least here on my end) when building such long dynamic templates and save/reload the template very often.
What I can do, if this is ok for you:
I will come back to you via email and a link to this post here as soon it happens again!
Best regards
Michael
@timmse Same happened to me yesterday. It took so much time and my IP was blocked by the server several times. Something was suspicious. But today all worked properly! I will send some server log entries to the help email address.
Hey Michael,
We have received your access data and have seen that you use a lot of dynamic data tags which lead to a lot of Ajax requests to render the elements again. This could possibly be a reason for the problem - we’ll look into it in detail.
@DavidKnecht Thanks for your logs and the access data, we’ll take a look too!
same happened yesterday to a minipage here. one section with flexible content. takes minutes to save and all get stuck.
News with Bricks 1.7 beta (might be v2 ?). This issue seems to be solved in my tests now. Saving now doesn’t crash my server anymore and lasts only 2-3 seconds (lasted 1-2 minutes before).
Thanks Bricks team for solving!
Thanks @beziehungsweise for the update.
Hi @OllieMackJo @Sashik @DavidKnecht @grafikundso ,
Appreciate your feedback if you have a chance to test on 1.7 beta.
Thank you!
Regards,
Jenn
back from skiing, 1.7 seems pretty stable in terms of saving and all. lag also got minimal. but a strange new issue poped up here about saving. Changes not saving, database connection lost, vanishing content - Bugs - Bricks Community Forum (bricksbuilder.io)
Hey @timmse
I seem to be having the same issue (Bricks v1.7.3).
Am seeing thousands of admin-ajax.php requests while working on some pages with dynamic data which quickly ramps up to 100% CPU usage on my 2GB DO server in Cloudways.
The main setup is ACSS, Frames, Metabox AIO, WPCodeBox, Woocommerce & WooCommerce Subscriptions.
Bricks also seems to have trouble rendering query loops using Woo Products and takes 1-2 minutes to execute the query loop commands in the builder.
For now I have disabled the ‘render dynamic data’ setting and have increased the Heartbeat API frequency to 90 seconds in functions.php.
Will monitor for now.
If you want to look closer, let me know.
Cheers,
Hi @johnnyhatz ,
Could you please provide temp admin access and send it to help@bricksbuilder.io?
Kindly include this thread URL as a reference in the email as well.
Regards,
Jenn