Posted by Gilles Ganault on 01/18/08 03:47

On Thu, 17 Jan 2008 20:30:10 -0500, Jerry Stuckle
<jstucklex@attglobal.net> wrote:
>The real question here is though - are you observing performance
>problems? Or are you prematurely optimizing?

I'm going step by step so as to understand where performance can be a
problem. It makes sense that we should avoid having the PHP
interpreter needlessly reparsing pages it already parsed into opcode
before, but I'm clear as to what I _shouldn't_ include in a PHP page
so that it's kept in the cache by the accelerator.

>And if you are having performance problems, what is the source of your
>problems?

Without experience in this sort of thing, it's difficult to tell. A
big "load average" as reporter by top (60 instead of below 1) is
apparently a big sign of overload, but we're having a difficult time
tracking down where the problem lies. Maybe 400 sleeping processes and
15MB Apache processes are a sign of bad I/O (hard-disk, network, or
MySQL waiting to service queries).

It's just an opportunity for me to really get down to how LAMP
applications should be built so they can scale beyond a few ten's of
users.

[Back to original message]