[snip] > I fourth the thing about database access. As long as > you realize that > reading from disk isn't the fastest thing around > either. Make sure you > reduce the number of files to be read to as little > as possible. And output > with something like readfile() to prevent the files > being loaded into > memory.
[/snip] A filesystem hit is a filesystem hit whether your requesting a php file or an image for a button. If you are worried about filesystem hits then shouldn't you also be worried about uneccessarily using GIF's etc. in your page layouts. Likewise cleaning up bloated HTML code and properly using CSS can cut down page filesizes dramatically, saving bandwidth for the server and clients. If users are potentially using dialup, cutting 20K off your pages will make them a lot happier than shaving a couple tenths of a second off the backend processes. (not saying you should not be performance focused on the backend as well.) olinux __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
