Fresh Concrete5 installation is extremely slow
Permalink
Yes, I know, this has been mentioned several times.. Cache here, cache there, opcache, and all that. But for a fresh install, these things really shouldn't be necessary..
Here's the gist of it. I'm running Bash on Ubuntu on Windows, nginx and PHP 7 and MariaDB through Valet. A regular PHP-file that echoes "Test" loads in < 70ms. Yes, it's not blazingly fast.. But it's barely noticeable.
But when attempting to create a theme on a fresh Concrete5 installation, where full.php just outputs "Test", it takes *> 5 seconds*, on *each* load, in Incognito, while logged out.. I don't have have any extensions installed or anything. Just a simple .
This is ridiculous. I have an 8th gen i7 processor and an SSD hard drive. I honestly can't believe that 3 years later, Concrete5 is just as slow as it used to be when I used it for the first time. How can this not be a priority?
This is the second time I use Concrete5 to build a website for a customer. I was hoping that in the three years since I last used Concrete5, at least the performance would be better. Three years, and nobody bothered to even attempt to figure out how to make it faster? Since then, a completely new major version has been released.. What have ya'll been doing?
I'm happy that this was my main priority this time, and I'm sorry to say that although the concept of Concrete5 is lovely, unless the issue of performance can be solved over the weekend, I'll have to find another CMS with drag and drop modules or build my own...
Please prioritize this in some nearby release.. I realize you won't be able to figure it out over the weekend.. And unfortunately, I currently don't have the time to dig into how Concrete5 is built... But neglecting how slow Concrete5 is, and replying to every person attempting to figure out how their servers are set up, is ridiculous.. That's not the main issue.. The main issue is the core. The dispatcher is way too slow..
Can someone at least tell me why this hasn't been improved in three years? Is there something making it difficult? Do you know what the issue is, but are not able to solve it without rewriting large parts of the core? Or is it just that nobody has bothered to figure out why it's so slow?
Thanks in advance..
And sorry for the harsh tone.. I had my hopes up, and am just a bit disappointed.. Although, I do realize that this is a free and open source CMS, and that it's kind of my responsibility as a developer to contribute if I find it lacking.. Hopefully I will in the future.. But right now I'm not able to due to work.. For now, I guess I'd just be happy with some answers to the questions I asked, and maybe a collaborative attempt at finding a solution..
Thanks again.
Here's the gist of it. I'm running Bash on Ubuntu on Windows, nginx and PHP 7 and MariaDB through Valet. A regular PHP-file that echoes "Test" loads in < 70ms. Yes, it's not blazingly fast.. But it's barely noticeable.
But when attempting to create a theme on a fresh Concrete5 installation, where full.php just outputs "Test", it takes *> 5 seconds*, on *each* load, in Incognito, while logged out.. I don't have have any extensions installed or anything. Just a simple .
This is ridiculous. I have an 8th gen i7 processor and an SSD hard drive. I honestly can't believe that 3 years later, Concrete5 is just as slow as it used to be when I used it for the first time. How can this not be a priority?
This is the second time I use Concrete5 to build a website for a customer. I was hoping that in the three years since I last used Concrete5, at least the performance would be better. Three years, and nobody bothered to even attempt to figure out how to make it faster? Since then, a completely new major version has been released.. What have ya'll been doing?
I'm happy that this was my main priority this time, and I'm sorry to say that although the concept of Concrete5 is lovely, unless the issue of performance can be solved over the weekend, I'll have to find another CMS with drag and drop modules or build my own...
Please prioritize this in some nearby release.. I realize you won't be able to figure it out over the weekend.. And unfortunately, I currently don't have the time to dig into how Concrete5 is built... But neglecting how slow Concrete5 is, and replying to every person attempting to figure out how their servers are set up, is ridiculous.. That's not the main issue.. The main issue is the core. The dispatcher is way too slow..
Can someone at least tell me why this hasn't been improved in three years? Is there something making it difficult? Do you know what the issue is, but are not able to solve it without rewriting large parts of the core? Or is it just that nobody has bothered to figure out why it's so slow?
Thanks in advance..
And sorry for the harsh tone.. I had my hopes up, and am just a bit disappointed.. Although, I do realize that this is a free and open source CMS, and that it's kind of my responsibility as a developer to contribute if I find it lacking.. Hopefully I will in the future.. But right now I'm not able to due to work.. For now, I guess I'd just be happy with some answers to the questions I asked, and maybe a collaborative attempt at finding a solution..
Thanks again.
Thanks for your reply.
I've edited my post, but I'll say it here as well. I'm already running MariaDB through Valet as well, meaning that it's already running on localhost/ 127.0.01
Regarding page statistics: I googled but couldn't find anything other than for a legacy version of Concrete5? Where can I find this setting for Concrete5 8.4.4?
I've edited my post, but I'll say it here as well. I'm already running MariaDB through Valet as well, meaning that it's already running on localhost/ 127.0.01
Regarding page statistics: I googled but couldn't find anything other than for a legacy version of Concrete5? Where can I find this setting for Concrete5 8.4.4?
Whilst C5 can be a hog, it wouldn't normally be that slow on such a dev system.
What sort of response time do you get on a clean Elemental install with sample content? - this will help indicate whether it is something in your theme or content that is inefficient (often over- use of attributes in headers or unconstrained autonavs), or whether its a system issue (resources, php setup, MySQL setup, Apache setup, fastCGI etc.)
What sort of response time do you get on a clean Elemental install with sample content? - this will help indicate whether it is something in your theme or content that is inefficient (often over- use of attributes in headers or unconstrained autonavs), or whether its a system issue (resources, php setup, MySQL setup, Apache setup, fastCGI etc.)
Hi John, thanks for your reply.
The first post I made was with an empty theme. However:
After having rebooted my system, a clean Elemental theme takes 2.5 seconds to load the home-page. That's better, but it's still slow. A completely empty theme with just "test" as content, takes ~550ms to load. That's much better, but still relatively slow.
If I comment out the dispatcher completely, and just echo "test", it takes 30ms to load. That's what I'm aiming for. As it stands right now, neither I nor my customer can accept the speeds required to load a page with no content in > 500ms.
I understand the need of using a cache when the page is full of JavaScript and images, but with no content at all, I really can't understand why it's so slow.
Does anyone know the details of what the dispatcher does? Has anyone spent any time on it? I mean I get the gist of it, but like, has anyone dug into it and tried to understand it? Why it's consuming time?
The first post I made was with an empty theme. However:
After having rebooted my system, a clean Elemental theme takes 2.5 seconds to load the home-page. That's better, but it's still slow. A completely empty theme with just "test" as content, takes ~550ms to load. That's much better, but still relatively slow.
If I comment out the dispatcher completely, and just echo "test", it takes 30ms to load. That's what I'm aiming for. As it stands right now, neither I nor my customer can accept the speeds required to load a page with no content in > 500ms.
I understand the need of using a cache when the page is full of JavaScript and images, but with no content at all, I really can't understand why it's so slow.
Does anyone know the details of what the dispatcher does? Has anyone spent any time on it? I mean I get the gist of it, but like, has anyone dug into it and tried to understand it? Why it's consuming time?
Hey nemocaligo
I've never had a problem with download speeds of the concrete5 site I have built. Most of the sites I build are under 3 second for page load time and that is with several plugins on the site.
I've never had a problem with download speeds of the concrete5 site I have built. Most of the sites I build are under 3 second for page load time and that is with several plugins on the site.
Hi stewblack, thanks for your reply.
3 seconds is kinda slow though. In my case, after having rebooted my system, an empty theme with no plugins takes ~550ms to load. That's also slow. What'll happen when I start including JavaScript and images?
3 seconds is kinda slow though. In my case, after having rebooted my system, an empty theme with no plugins takes ~550ms to load. That's also slow. What'll happen when I start including JavaScript and images?
Here is a great blog by A3020 one of the main contributors to C5 on how to make C5 sites fast. https://a3020.com/blog/the-ultimate-guide-to-a-fast-concrete5-websit...
Thanks, I'll try out some of the tips listed here. Although, one would think none of this should be necessary for an empty theme with no plugins, :/
It seems that the database address, setting to 127.0.0.1 i gain some speed.
Also turn OFF : Page Statistics