CPU Load shot up, so did Usage:

I just followed Pierre's link and read this:
I also came across this thread, so am reading the six pages to see if this is the solution I'm looking for which will fix my client's hosting/CPU Load issues:Cache is a collection of tags that stores output of some other tags (content, stylesheets) in temporary files so it will be more static. It's a quick'n dirty solution for some CMSms speed problems ...
Latest Release
cache
Cache 1.01
2007-01-08 Release
Hi there Viebig!viebig wrote: Are you using xcache/apc? Stylesheet cache
Regards
For stylesheet caching, I believe viebig is referring to the option in the CMSMS Global Settings menu:WebGirl wrote:Hi there Viebig!viebig wrote: Are you using xcache/apc? Stylesheet cache
Regards
I'm not sure what "xcache/apc" and "Stylesheet cache" are, or how I use them.
Are they part of cmsms or php?
Hi Pierre, I'm sorry, but I don't know what "bottom of source of page numbers" means.Pierre M. wrote: Yes, less installed modules and less db queries.
BTW, what are your "bottom of source of page" numbers ?
Pierre M.
Jeremy - re Global Content Blocks - I had no idea that we shouldn't use these. I use them for my own sites and client sites for Google Adsense and other info.----------------------------------------------
Cms Version: 1.5.4
Installed Modules:
* CMSMailer: 1.73.14
* ModuleManager: 1.2.1
* FormBuilder: 0.5.3
* nuSOAP: 1.0.1
* Search: 1.5.3
* ThemeManager: 1.1.0
* Comments: 1.8.1
* Captcha: 0.4
* MenuManager: 1.5.3
* News: 2.9.3
* TinyMCE: 2.4.13
* FileManager: 0.4.5
* Printing: 0.2.6
Config Information:
* php_memory_limit:
* process_whole_template: false
* max_upload_size: 10000000
* default_upload_permission: 664
* assume_mod_rewrite: true
* page_extension: .html
* internal_pretty_urls: false
* use_hierarchy: false
Php Information:
* phpversion: 5.2.1
* md5_function: On (True)
* gd_version: 2
* tempnam_function: On (True)
* magic_quotes_runtime: Off (False)
* memory_limit: 128M
* max_execution_time: 60
* safe_mode: Off (False)
* session_save_path: /tmp (0777)
Server Information:
* Server Api: cgi-fcgi
* Server Db Type: MySQL (mysql)
* Server Db Version: 4.1.11
----------------------------------------------
Viebig, I have noticed in the web states for my client site that stylesheets.php gets thousands of hits a week - the top two are cmsms:CMSMS stylesheet generation can slow down the site, depending on how many you use. You can use static stylesheets or look for modules that export static stylesheets.
I asked the hosting support team about this and this is their reply:Q: I'm not sure what "xcache/apc" and "Stylesheet cache" are, or how I use them.
A: xcache, eaccelerator, send optimizer, apc are opcode cachers that can be installed on the server and enabled in the php configuration.
This is now quite a problem, and I'm wondering if I have to find a new hosting solution for my clients. CPU Load allowance is 4.5%I am afraid that unfortunately we cannot install opcode on the server and we already have APC Cache for PHP installed which is much better that the offered.
This seems crazy - we must be able to sort this within cmsms without my client having to pay $60/month.A temp solution would be a semi-dedicated server for $60/mo with 15% CPU or for $90/mo with 25% CPU.
I understand that you do not wish to expand for now but a dedicated server is a great investment, especially since you expect the traffic to your sites to increase.
!-- 0.358987 / 61 / 8494964 / 8648356 --The source numbers he was talking about are found by viewing the source for the page in the browser and looking at the last line.
I didn't know I was supposed to change this, didn't read it in documentation - or perhaps I missed it somewhere?What is your setting for stylesheet cache in your system admin?
There's no indication what 'relatively high' means - 1,000? 10,000? 100,000? - so I followed the number on the forum post I mentioned above - 604800.Maximum amount of time (seconds) stylesheets can be cached in the browser:
Was = 1000
Just changed to = 604800 (as per this post http://forum.cmsmadesimple.org/index.ph ... #msg160354
This parameter should be set relatively high for static sites, and should be set to 0 for site development
The client is working on her site every few days - in this case, the week setting is probably ok.from 1 hour = 3600 seconds
1 day = 86400 seconds
1 week = 604800 seconds
http://forum.cmsmadesimple.org/index.ph ... #msg160354
I didn't say "we shouldn't use these". It's like wine, good for the heart but too much and it's bad for the liver. What I was suggesting is to think of every {} as time for CPU/RAM/database to happen... think of ways to do the same thing without a GCB as you’ll cut CPU/RAM/database. One thing I do is if the GCB is in the main template then I just put it straight in as my clients never see that area so it's a safe place to put the smarty code.WebGirl wrote:- re Global Content Blocks - I had no idea that we shouldn't use these. I use them for my own sites and client sites for Google Adsense and other info.