Serious concerns regarding Brizy Cloud Architecture
We've helped our clients launch a number of website with Brizy Cloud. We're happy with the page builder and the ease of use.
Our serious issue with Brizy Cloudhas to do with how page generation is handled. It is something that our clients are not happy with and that we're getting an increasing amount of feedback on. As we're trying to move away from self-hosted Drupal websites in the future, we have several dozen websites that we need to find a new home for. This is an issue that is making us rethink our commitment to Brizy Cloud.
The issue is this: When a page is saved in Brizy Cloud the next page load will take upwards of 10-15 seconds. This is an issue that is present on every single project, website and page. It should be extremely easy to reproduce. If I publish any type of change on the front page of a website, that page will then take 10+ seconds to load. As if this is not bad enough, this same problem will now trigger across every single page on the entire website. The only workaround is for us or our client to manually visit every single page and news post across the entire website - every time anything changes on the website. This is not sustainable and I'd like to know what is being done to resolve this, what we can expect and a timeline for a solution. Me and my colleagues have tried to ask this question repeatedly but we are not getting any concrete information. This has to be of serious concern to you as well.
-
Hi Mattias,
We are aware of this issue. When you visit a page the first time after making an update, the page is recompiled and cached. This takes a while. The second time onwards the page loads from the cache much faster.
We are working on a new compiler to overcome this issue. Its difficult to predict when this feature would be released though.
0
Please sign in to leave a comment.
Comments
1 comment