script efficiency (parsing, and large scripts)

[zeb]

I have ended up with a script over 3500 lines. Everything is broken up into functions, so only the code that is needed is parsed every time the page is accessed. My question is whether or not it would be more efficient to break the script into separate files to include appropriately, or if having a large file containing all the functions is fine?

I have received a comment about the pages loading slowly - I have yet to determine if it's the script execution, or if it's the bandwidth, but I thought I'd ask.

[iamjbrandt]

PERSONALLY, I believe it may be a combination of both. A slow server will, of course, slow things down, but I think having a large file with everything in it does tend to slow it down more. I would always try to keep my files no more than 30kb, but I don't think you would have to go THAT extreme, just less than 3,500 lines in every file would be good. Maybe break it into 3 pieces and see if it works better? Does that help you at all?

• Jared

[zeb]

I guess I was wondering more specifically how the PHP parser works. Does having a large file full of functions affect the speed at which the parser executes a given chain of events throughout the script? Say for example the HTML request requires the script to use three of the functions within this 3500+ line file; would it execute faster if the three functions existed all by themselves in a file - or does the rest of the larger file become immaterial?

Does that make sense?

[superwormy]

I have found that multiple files actually slows down your scripts, because PHP's gonna have to hit the hard drive to get the files on every call to include() or require()

BUT I would time it, test it, and see which works better.

I think that multiple files is often the more organized and neater way to do things.