Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46889
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.222.178 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=jNnFuRgUVhgIJJTb8NiL48h6dhT7At/M8HQ3vHSi5S2aslih8Ts0QbTAKpTY+7ePPx
         WkTHUsH2/dODiv285hcySTZxdexhKdE5R/c4sxjJUBC0HnEj8aGeGKD/QZS4eWpKN9hf
         9nt5ZDvqLKwy6CiwzOV8IdiJjw072dO+Lyt9A=
MIME-Version: 1.0
Date: Tue, 26 Jan 2010 11:15:17 -0800
Message-ID: <57792e851001261115n7a5d2b3fs51c16e0293685c09@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] About optimization -- What every programmer should know 
	about memory
From: iamstever@gmail.com (steve)

Just as a reference point should someone come across this thread at a
later date, and are interested in how memory usage changes
performance, this was one of the articles I found that does a decent
job, somewhat dated:

What every programmer should know about memory
http://lwn.net/Articles/250967/

You can look at the part about what programmers can do:
http://lwn.net/Articles/255364/

And don't forget about the tools like valgrind and perfctr. Also
oprofile, pagein, pfmon, callgrind.

iam

On Mon, Jan 25, 2010 at 4:59 PM, steve <iamstever@gmail.com> wrote:
>> This isn't about server costs. =A0It is about choosing the right tool fo=
r
>> the right part of the job. =A0A Javascript library for the client-side
>> frontend, PHP for the server-side frontend, C/C++ for your middle-layer
>> and an appropriate datastore behind it all and you can build amazing
>> things with PHP. =A0The largest destinations on the Web today are writte=
n
>> exactly like this.
>
> This is a tremendous insight. No where near my experience. (Neither is
> cheap hosting for individuals). Faster PHP means smaller webfarm, and
> if you pay for that webfarm, then these things matter. At any rate,
> thanks for the long description. And I do notice the nice tone in
> contrast to mine that day. Sigh...
>
>> All I can say on this is, send some patches to the list. =A0PHP improves=
 through code.
>
> True, true. But I remember a history of push back to such things, and
> even if now that is no longer the case, the price of political
> engagement is too high (that is, just explaining the stuff, etc).
> We're at the point of migrating away (in small tiny steps) anyhow, but
> I hope others that have experience and extra manpower speak up. There
> are some interesting internal forks of php out there that are cleaner
> and faster than what we could contribute anyhow.
>
>> It seems that you did not look closely to the improvements made to PHP 5=
.3.
>
> Sadly, I'm not sure 5.3 is in the cards for this year, and the stock
> build wouldn't do. Needs work on method dispatch.
>
> iamstever
>