Memory & Processor Usage
Permalink
Hello All,
I am currently in the process of creating content for my first real world Concrete5 site. I continue to be very very impressed by Concrete. However, I have noted that my server was being subject to some pretty intensive use during my editing sessions. I host with eApps and currently I am being told that I have 46% CPU usage with 146 Mb of memory usage. Strikes me as being a lot! Is this normal?
I am currently in the process of creating content for my first real world Concrete5 site. I continue to be very very impressed by Concrete. However, I have noted that my server was being subject to some pretty intensive use during my editing sessions. I host with eApps and currently I am being told that I have 46% CPU usage with 146 Mb of memory usage. Strikes me as being a lot! Is this normal?
Thanks. I have started using eAccelerator and noted a very significant drop in processor usage. Nevertheless the high processor load when I was the only user - still developing the site - took me by surprise. I have developed Drupal sites in the past and not noticed this issue. I hasten to add that there is nothing in the universe that would ever persuade me to develop Drupal again. Concrete is quite simply the best CMS around.
It's always been CPU and RAM heavy, no problems once the site is live but lots of editing does seem to suck up those resources.
What may be a good idea for you if your server is suffering is to do your build off line on XAMPP or similar.
This means your local machine takes all the strain and is also more able to handle it. Once you got your site looking the way you want it then transfer it to your server.
Minor edits and changes can then be comfortably done on the server after the site is uploaded.
What may be a good idea for you if your server is suffering is to do your build off line on XAMPP or similar.
This means your local machine takes all the strain and is also more able to handle it. Once you got your site looking the way you want it then transfer it to your server.
Minor edits and changes can then be comfortably done on the server after the site is uploaded.
I have a local WAMP installation and hand considered doing the site development locally. However, I was not sure how I could port the whole site across to my server later without breaking links etc.
Porting a site wont break any links, you just have to look at your site.php to see what changes are needed.
There are several useful post on how to do it (do a search on this site)or if you want to know more about the topic and much much more then you may want to buy a copy of Remo's book, Concrete 5 for Beginners.
There are several useful post on how to do it (do a search on this site)or if you want to know more about the topic and much much more then you may want to buy a copy of Remo's book, Concrete 5 for Beginners.
C5 has a caching feature which is useful. Make sure you're using that in production. I serve a couple of C5 sites with IIS. I take a bit of a performance hit for that myself, but I have it tweaked fairly well. There's also PHP extensions for improving PHP processing time. I read the other day that the next version of PHP is suppose to have opcode caching built into it, which will be very cool.
http://en.wikipedia.org/wiki/List_of_PHP_accelerators...