Concrete5 very slow with database on remote computer
Permalink
We're working off of macintoshes running apache and php as development machines and using a shared database on a linux server. Other PHP sites such as wordpress or rails sites work fine in this configuration. However, Concrete5 is going very slow. The pages process fine, but it takes like 10 seconds or more sometimes just for the php file to render, and then other files like .js take a long time as well.
If i copy the database locally its fine--no performance problems. If I run Concrete on our linux server and point its config to localhost its fine. The issue is performance whenever mysql is on a remote server. I have tried changing the host to be just the local network ip and that doesn't help either, so doesn't seem to be dns.
Help!
If i copy the database locally its fine--no performance problems. If I run Concrete on our linux server and point its config to localhost its fine. The issue is performance whenever mysql is on a remote server. I have tried changing the host to be just the local network ip and that doesn't help either, so doesn't seem to be dns.
Help!
this is a known issue.
ah, well good to know. Any ETA on the next update that will have it resolved?
I don't know if it will be fixed, it doesn't affect very many people.
Ok... Any idea where to look for in order to get that fixed? I don't mind sorting it out... but if I can get a psuh, it would be nice...
Thanks,
Thanks,
bump! This doesnt seem fixed in the last update.
Bump, been working on this site with GIT and it's awful. Up to 30secs wait time in the back end when working locally. Yawn.
I'm not really sure what we can do about this. We've worked on plenty of sites where the database server is separate from the main web server and it's worked fine.
Did you ever happen to find a solution for this fregas?
@concrete5 responded to me on twitter about this actually.
They suggested you just work locally, which obviously isn't the best method of working if you want multiple devs on 1 project.
After pointing this out they responded with:
@lexbi if you really want to connect to a remote database from a local install, you're going to have to explore latency in that connection
@lexbi the current version of concrete5 certainly demands lots of database queries, the next one will optimize that more.
They suggested you just work locally, which obviously isn't the best method of working if you want multiple devs on 1 project.
After pointing this out they responded with:
@lexbi if you really want to connect to a remote database from a local install, you're going to have to explore latency in that connection
@lexbi the current version of concrete5 certainly demands lots of database queries, the next one will optimize that more.
I'm surprised it's not more of an issue. Working locally is fine for one person on one machine, but as you've mentioned, it's a huge pain for multiple devs or even multiple machines. Cheers for the heads up.
what a pain :(, just experienced the same issue, normally works fine, but we have just set up Vagrant and noticed a significant drop in speed.
It is 2016 and the problem is still there. All other CMSes work fine but C5 is very slow connecting to an external database. Why is that? Internal logic relying too much on the database? I've seen other CMSes do that and that was their downfall. Perhaps you are trying to be too clever for no good reason.
