Hosting issues - Help
Permalink
Ive got three related sites on concrete5's hosting at liquidweb. One is running 5.6.0.1 and the other two are running 5.5.2.1.
The older ones are faster by 10x right now. Anyone have an idea why?
http://www.premieradvantagemarketing.com/... is 5.5.2.1
http://www.budco.com/ is 5.6.0.1 which is occasionally throwing errors like:
"Fatal error: Exception thrown without a stack frame in Unknown on line 0"
The older ones are faster by 10x right now. Anyone have an idea why?
http://www.premieradvantagemarketing.com/... is 5.5.2.1
http://www.budco.com/ is 5.6.0.1 which is occasionally throwing errors like:
"Fatal error: Exception thrown without a stack frame in Unknown on line 0"
Sounds like it could be due to FastCGI being on the hosting server. I know if I leave it on on my servers it slows them down.
We are also seeing this same issue with FastCGI.
Hi tallacman,
I emailed you a moment ago but we thought it would be a good idea to post this information here and elaborate a bit as well.
What we've done to help improve performance on your 5.6.0.1 site is enable the Overrides Cache. This is a new feature introduced in concrete5.6, and it lets us store existing overrides in the database rather than doing the usual checks (overrides directories, then the package directories, then the core directories...). This can improve performance.
If a 5.6.x site (such as the site in question) has more than a few overrides in place-- and the Overrides Cache is disabled-- it might actually run slower than a 5.5.x site. This is because the site is actually computing all overrides upon each page request, regardless of whether or not the actual override files are required by the page rendered. Once the Overrides Cache is enabled, it should run as fast as, if not faster than a 5.5.x site. It's an important distinction to be aware of.
Another detail concrete5 developers should be aware of is that we leave the overrides cache disabled on upgrade to 5.6. So if you're upgrading a site with a lot of overrides, it's something you should likely turn on while you're checking things out, post-upgrade. New installations however, will start off with the Overrides Cache enabled.
Hope that helps explain what's going on behind-the-scenes in the Overrides Cache. Turning it on for your 5.6.0.1 site seems to have restored the site's performance to what it was prior to upgrade.
For anyone else reading this thread in the future: to turn it on, go to Dashboard > System & Settings > Optimization > Cache & Speed Settings. I've attached a screenshot of what this looks like in 5.6.
I emailed you a moment ago but we thought it would be a good idea to post this information here and elaborate a bit as well.
What we've done to help improve performance on your 5.6.0.1 site is enable the Overrides Cache. This is a new feature introduced in concrete5.6, and it lets us store existing overrides in the database rather than doing the usual checks (overrides directories, then the package directories, then the core directories...). This can improve performance.
If a 5.6.x site (such as the site in question) has more than a few overrides in place-- and the Overrides Cache is disabled-- it might actually run slower than a 5.5.x site. This is because the site is actually computing all overrides upon each page request, regardless of whether or not the actual override files are required by the page rendered. Once the Overrides Cache is enabled, it should run as fast as, if not faster than a 5.5.x site. It's an important distinction to be aware of.
Another detail concrete5 developers should be aware of is that we leave the overrides cache disabled on upgrade to 5.6. So if you're upgrading a site with a lot of overrides, it's something you should likely turn on while you're checking things out, post-upgrade. New installations however, will start off with the Overrides Cache enabled.
Hope that helps explain what's going on behind-the-scenes in the Overrides Cache. Turning it on for your 5.6.0.1 site seems to have restored the site's performance to what it was prior to upgrade.
For anyone else reading this thread in the future: to turn it on, go to Dashboard > System & Settings > Optimization > Cache & Speed Settings. I've attached a screenshot of what this looks like in 5.6.
Thank you. That IS great support!
The cache settings are actually optimized by default when you install 5.6.0.1. No need to worry there...I think what the problem was for him is that it carried the settings over from 5.5. 4 installs of 5.6.0.1 for me and they are all defaulted to Speed up live site.
Keep in mind that there are two different caches that are controlled from that same page in concrete5.6:
1) the standard site cache.
2) the new Overrides cache.
These are different. During upgrade to 5.6, a site will keep whatever standard cache options it currently has. But since 5.6 introduces the new Overrides Cache, this is by default set to disabled.
If you're performing a new installation, both caches will be enabled.
1) the standard site cache.
2) the new Overrides cache.
These are different. During upgrade to 5.6, a site will keep whatever standard cache options it currently has. But since 5.6 introduces the new Overrides Cache, this is by default set to disabled.
If you're performing a new installation, both caches will be enabled.
Yeah I have seen the new overrides cache option...mine was on by default on all installations of 5.6.0.1. So I am guessing upgrades will not do it automatically because of it being a new added feature.
Good to know.
Good to know.
How is this override cache cleared?
that we're working on.
best wishes
Franz Maruna
CEO - concrete5.org
http://about.me/frz