#1 (permalink)

Hello im looking for someone to decrease my server usage load the site is
ietv .co .uk

I got this message from my host;

" When I first went to the site to troublshoot it was locked up once again
with the memory graphs maxed out. I restarted it and watched it for over
2 hours until the usage slowly climbed to 1500, looking to be on a steady
trend up. There are currently 81 live processes under your free**** user
typically using 15MB of RAM each. That would be 81 processes with 101
connections. It seems like there is likely a lot that could be done to
cache your code so that PHP processes aren't triggered to eat up RAM and
efficiently die each time they are triggered b a page load. I would
suggest auditing your sites code to make it use caching so so many
processes aren't spawned."

Any help will me much appreciated.

Cheers
Tom

#2 (permalink)

I have some experience with code and processes optimization.
What kind of site do you run? Buyed script, or hand coded?
If buyed, which one.

What kind of server, what specs ?
What services are used ?

What language does your site runs?

__________________
Only a biker knows why a dog sticks his head out the window.

#3 (permalink)

Site is based on a free bloging system Wordpress
On a VPS at dreamhost 1999 MHz of CPU time and 1999 MB
Sites run on PHP

Hope that Helps

Cheers
Tom

#4 (permalink)

How much ability do you have to modify the VPS that you're on?

I'm not offering to do anything for you, but look into implementing "lighty" lighthttpd. I believe http://howtoforge.com has a few articles on how to implement it.

Lighty acts as a front-end to your apache server. Any requests that come in for static content (most CSS, JS, Images, etc...) are served by lighty. It never tries to serve any dynamic content. Because of this, it's proccess sizes never grow larger than about 2MB. Currently, all of your files are being served by Apache. Once Apache serves PHP content, its proccesses will grow to between 15 and 20MB on average. However, those ultra-large processes will also serve the same static content, which could be handled much easier by a smaller process. So, lighty handles the static content, and apache only gets passed the dynamic requests, which means it can handle it with fewer proccesses. I've found with most CMS software, upwards of 70% of the http requests you see are for static content....

That being said, optimzing your code and setup is also a good idea.

#5 (permalink)

Thanks for your tips. Still looking for someone

Tom

#6 (permalink)

Since it is on VPS and you ought to have root access, you should be able to install some php accelerator witout any problems. You may try http://eaccelerator.net/ for example.