Re: Function caching...

Zeev Suraski wrote: > When I see Kristian saying that it's fine 'as long as you > follow a few simple rules', I know we have an error-prone feature in front > of us. For Kristian it may be simple (which I doubt, by the way), but bare > in mind that Kristian and you are hardly the average users. Simple things should be simple. Complex things should be possible. That's why PHP has OO and why PHP without OO is simply not acceptable (it would have been okay in 1970). > You said that increasing hardware is not good scalability. That's wrong - > this *is* scalability. Scalability means you can get 2x (or close to 2x) > performance if you increase the power of your hardware by 2x. And then there is a whole bunch of _really_ _sucky_ _coding_ where increasing hardware won't help you a bit, only better code will. Talk about cubic solutions to logarithmic problems. Or simply stupid execution models - today I downsized a newspaper's website from a four processor U-450 to a Netra T1. By using simple script result caching, by the way (3 line change in a perl script - not worth mentioning, except that it brought down the load from over 25 to below 1). Kristian -- Kristian Köhntopp, NetUSE AG Siemenswall, D-24107 Kiel Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 Using PHP3? See our web development library at http://phplib.netuse.de/