|
|
Posted by Jerry Stuckle on 01/18/08 04:36
Gilles Ganault wrote:
> 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.
>
Don't. Find your performance problem. 99%+ have absolutely nothing to
do with the interpreter, and an accelerator will make no noticeable
difference.
>> 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).
>
Then get a sysadmin who is experienced in it. Otherwise you're shooting
in the dark. You can eventually find it. It may take you a few months,
though.
> 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.
>
This most probably has nothing ti do with "how LAMP applications should
be built". More likely it's lack of resources on the server.
Get a good Linux sysadmin. You can find consultants. It will be worth
the money.
And go to a Linux support group to find out what's going on with your
system.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|