Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44073
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.157 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=r0Zcx8Y/ct3mn5qNeFX1XvLPqV7mzysZkcZP49eKycOmPFjalRgv4hO9eAZrQO5KUE
         JDDHYlste5MkLiz+QZXmyLvp7yABQKHJL31cOKAStUkqmR+wqc4Aj9QMKHTvQaw7+7hP
         GXbXwaG2ObGvOXynf3cOUglpm8NmVnF4RLgyM=
MIME-Version: 1.0
In-Reply-To: <826683.74097.qm@web110405.mail.gq1.yahoo.com>
References: <826683.74097.qm@web110405.mail.gq1.yahoo.com>
Date: Tue, 26 May 2009 22:55:53 -0400
Message-ID: <68de37340905261955r51175134n4a1c6881cd3a76b9@mail.gmail.com>
To: tRace DOliveira <married_74@yahoo.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001485f2716055a508046adbfb81
Subject: Re: [PHP-DEV] PHP scalability problem
From: oorza2k5@gmail.com (Eddie Drapkin)

--001485f2716055a508046adbfb81
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

1) PHP is Rarely The Bottleneck:
http://talks.php.net/show/drupal08/<http://talks.php.net/show/drupal08/7>
2) Invest in an opcode cache
3) DB I/O is always the most restrictive part of your application, read the
mysql performance blog (a lot applies for postgres too)
4) If you're serious about scalability, ditch apache and use a better
webserver
5) You're describing what ajax does in a lot of cases
6) Have you deployed flatfile cache / apc / memcached?  If so, how?
7) Do you regularly run siege tests on new server stacks and profile each
piece's impact on performance?
8) Do you profile your code every time you change some piece of logic?

Scalability is an enormous mountain to climb and there's only so much you
can offload on to the client.  Chances are there's more room for improvement
at any stage in your development than there is potentiality for client-side
processing.

On Tue, May 26, 2009 at 10:46 PM, tRace DOliveira <married_74@yahoo.com>wrote:

> PHP is a server side scripting language, so that means that the server will
> have to do the bulk of the processing if not most.
> I was thinking about shifting the processing to the client. Kinda like how
> java does it. I don't know really know how java does it but it would be
> interesting if it could be done for PHP also.
> Thank you,
> Leonard D'Oliveira
>
>
>

--001485f2716055a508046adbfb81--