# About optimization -- What every programmer should know about memory

- Thread: https://externals.io/message/46889
- Original archive: https://news-web.php.net/php.internals/46889
- Started by steve on 2010-01-26T19:15:17+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #46889 — steve — 2010-01-26T19:15:17+00:00

URL: https://externals.io/message/46889#46889

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


> > […]
>
> 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...
>
> > […]
>
> 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.
>
> > […]
>
> 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