I noticed that when editing components, there is an unusual overload on the server.
If you want to test it, present the component several times on the same page.
With loops of different query instances, for example, one bringing sales, another bringing rent, and so on.
When trying to save or edit components in this situation, the experience is horrible.
These values go up to the maximum on the server:
Physical memory usage
CPU usage
IOPS
NOTE: I am not using a high-performance server, but so far I have never felt any shortage. Bricks has always been very fast in every way. If you are going to test it, please test it on a medium-sized, popular server, like most servers on the web
In other words, something in the components is causing this excessive consumption on the server.
I didn’t understand your question. It doesn’t seem to be related to the images, but rather to the component instances on the page. If I put more components on the same page, and the component has many dynamic fields, the page becomes very slow, especially in the administration. It even makes it impossible to make changes to it. Even saving doesn’t work.
first - I apologize for my delayed response here on the forum. Behind the scenes, we did investigate the reason for this. It comes down to many API request that the builder does while you are changing the elements.
We will investigate this in the future, and check how we can improve it.
