Posted by Toby A Inkster on 03/28/07 11:04

lister wrote:

> Am I worrying over nothing?

Probably.

Structure the code in the most logical manner -- don't let performance
issues cloud your judgement here. If you code entirely for performance,
then in two years' time, when average CPU speed is double what it is now,
and RAM costs have fallen through the floor, you'll be sitting on a bunch
of spaghetti code and cursing yourself.

When the project's nearing completion, and after proper performance
testing, if you find that it's performing poorly, then look at installing
some PHP acceleration software, such as eAccelerator, which caches
compiled copies of your files in memory.

http://en.wikipedia.org/wiki/Optimization_(computer_science)#When_to_optimize
http://www.solarisinternals.com/wiki/index.php/Performance_Antipatterns#Premature_Optimization
http://blog.astrumfutura.com/archives/211-.html

--
Toby A Inkster BSc (Hons) ARCS
Contact Me ~ http://tobyinkster.co.uk/contact
Geek of ~ HTML/SQL/Perl/PHP/Python*/Apache/Linux

* = I'm getting there!

• Next in forum: Re: explode
• Prev in forum: Two strange problems
• Thread view: Re: Performance impact of "require"ing lots of source?

[Reply to this message]