Seperated Function Files

[Webase]

Just wondering, I've always used seperated function files for organization and bandwidth saving purposes, but I want to know, is this really necessary? Do you guys recommending splitting the functions to save bandwidth, according to the user needs it'd be required?

[bradgrafelman]

Bandwidth? PHP code is parsed and processed on the server, no bandwidth is used...

[Webase]

No, but I mean like I have around 100kb of functions on php files, when I require that file 100kb of bandwidth is spent, isn't it?

[bradgrafelman]

Nope. Unless you're loading PHP source files from different servers (I highly doubt this), no bandwidth is used in the processing of PHP files. The only bandwidth used is the incomming bandwidth of the client's "GET /myscript.php HTTP/1.1" HTTP request, and then the outgoing bandwidth of PHP outputting the HTML data.

Now, what you are dealing with is hard drive seek time (to read the file's contents), and memory/CPU (for PHP to parse all of that). If your files are that large and you notice slow process times or more CPU/memory usage than you'd like, you might try spliting up functions into different files. Try to group them together and label the file accordingly.

[jdorsch]

Try setting it up so you only include the functions you need, instead of including every function on every page.

If you are on PHP 5, you are best to stop using functions, organize everything into objects/static objects, and then write an __autoinclude() function.