Page 3 of 3

Re: very slow site

Posted: Sat Feb 25, 2006 12:34 pm
by thumbsucker
I got script errors.

What's the best way to upgrade a version while keeping all present content, templates, etc?

I got a message from my host saying I'm exceeding CPU and RAM usage, so I'm curious how resource intensive CMS Made Simple might be....

Re: very slow site

Posted: Sat Feb 25, 2006 2:10 pm
by LeisureLarry
Upload all files of the new version and run uppdate.php instead of install.php. That should be all. But for 0.12 you have to change your templates because the old smarty tags for the menu aren´t supported any longer.

Re: very slow site

Posted: Fri Mar 31, 2006 11:50 pm
by Pierre M.
I agree with "sloop" (above in this thread) : serving pages is a static job, with no latency problem, no db access and even no CPU for PHP. Building/generating a page may take up to 15s but it should hurt the publisher only, not the surfer. Please see : http://forum.cmsmadesimple.org/index.ph ... 678.0.html

Whenever a page is changed, the static file is erased so the rebuild page is... changed ;)

Hope it helps

PM

Re: very slow site

Posted: Sat Apr 01, 2006 3:14 pm
by davidL
I find cmsms to be really nice, but it runs a little bit slow. Not as slow as thumbsuckers but anyway slow. On my site I have generation times of approximately 1.2-2.5 sec depending on cached, nr of sql enquierys etc. Is this normal? Is there anything in my system that could slow it down?

System info
Cmsms 0.12
Windows 2003 Server, IIS6
Php 5.1.1
MySQL 5.0.18
Server hardware: Dual P3 500mhz, 512mb ram, Scsi disk


The times written above are pretty much the same both for my custom website as well as the 0.12 clean install.

Re: very slow site

Posted: Sun Apr 02, 2006 9:37 am
by cyberman
Change from windows server to linux  ;) ... on my tests windows server eats 0,2 to 0,5 secs more than linux one.

Also with pimenu it's possible to create a little bit more static (and faster) pages.

Have you also read these hints?

Re: very slow site

Posted: Mon Apr 03, 2006 4:35 pm
by davidL
I figured the main problem was the windows server, but unfortunately I can’t do anything about that since I’m not the one running the server. I'm also getting the webspace for free so paying a webhotel for getting a linux server is currently not interesting. I tried the other tricks in your list and it did help a little (mainly uninstalling the modules and plugins not in use). Thanks!