Re: Some more plane hacking...

["Tomas V.V.Cox" <cox@idecnet.com>] > > Real sever page optimizations are minimizing the numbers of access to > disc. Ram, no external js, no external css, reduced number/size of > images, etc. Okay, say you've optimized away all the disk access, whatever there is left always comes from the disk cache. Your site uses ZendCache without timestamp validation and getcwd, and "top" shows 90/10 user/system CPU. You've tuned network buffers and Apache process pools. You really can't squeeze any more speed out of your PHP code or Apache configuration, and you are starting to fantasize about JIT compilers at night. That is a C rewrite of some strategic components becomes your halo-encrusted knight in shining armor. Your JIT nightmares go away, and you can start hacking again. I buy all your arguments about maintainability etc. But there are some things that either _must_ be done in C (efficient asynchronous IO, low-level database abstractions, GTK bindings or whatever) or that would have significant performance benefits for everyone (the PEAR and PEAR_Error classes will be used all over the place, why not save a file parse?) I'm talking about exceptions now of course. Most PEAR code will be 100% PHP. - Stig -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway