On Thu, 2004-02-05 at 16:12, vidyut luther wrote:
> Hi John,
> A couple of questions.. 
> 1. Define high load.
Er.. that's quite a personal question, apparently we get 58 million hits
a month but some days will be much busier than others (we're a soccer
site, match days are busiest). The load is split over 6 Dell Poweredge
1550 servers.

> 2. Why are the servers being restarted once a day ? There shouldn't be a
> need to restart unless something is going wrong. 
For cycling the logs, we've got scripts setup to sort them out each day
- backing them up and suchlike, which restart the webserver.

> 
> As for your main question.. I build php as a DSO module basically
> because I don't upgrade my PHP as often or whenever there is a new
> version out, unless it's got security fixes.. and even then I wait for
> everything to be tested. This helps out in the way that I don't have to
> upgrade or recompile two things whenever I want to update php , or
> apache. Secondly, it's easier to disable PHP this way, in case I have
> extremely high traffic and I only want to serve static content. But, to
> each their own.  The main speed/performance difference will come more
> from how you write your code than wether it's dynamically or statically
> built. Also, if you need performance increases, look into Zend
> Accelerator or the ZPS Suite.. (it's kinda expensive, but WELL WORTH THE
> $$). 
> 
> Please note i have no links with Zend other than being a very happy
> customer. 
> 
I get that the code is very important, some bits of our code are great
for efficiency, some less so great, I'm basically looking to squeeze the
best performance out of what we've got. (We use Zend Optimizer, not
tried the Accelerator yet).
John

> On Thu, 2004-02-05 at 09:28, John McKerrell wrote:
> > Hi,
> >    I've been working with a PHP for a few years now. I've always thought
> > that on production servers, to have them working at peak efficiency, I
> > should have the Apache and PHP compiled as a static build. I recently
> > got into a debate with someone over whether this had any worthwhile
> > savings. Can anyone tell me which is the best solution, or point me in
> > the direction of a solution? I realise that it would vary from situation
> > to situation, so I'll tell you that my situation is high load servers
> > required to run as fast as possible. They get restarted once a day, and
> > (ideally) only get php+apache rebuilt when there's new versions out.
> > Thanks for any advice you can offer,
> > John

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to