Wouldn't the PHP cache/optimizing add-ons make it so it doesn't matter
after the first time you run the script anyway? So even if the first
pass was a few milliseconds slower it wouldn't be on future executions?
Maxim Maletsky wrote:
> My advise to you is to care about the portability of software rather then
> it's speed.
> include() and require() are not too painful, not too slow. You can easily
> have 10 of them and by that your page will be slower by only few dozens of
> milliseconds. However doing so you could reuse some parts of your code
> having your software more dynamic.
>
> Cheers,
> Maxim Maletsky
>
> -----Original Message-----
> From: Soma Interesting [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 14, 2001 5:16 AM
> To: [EMAIL PROTECTED]
> Subject: [PHP] parse speed vs require speed
>
>
>
> I'm wondering if I should organize the functions for my project into a
> single large file and have only one include/require, or break the code out
> into separate function library files and use a number of includes/requires.
>
> With a single large function library I'm guessing PHP would parse this
> every time a page is called. So I could loose some overhead by separating
> my database functions into one file, my administration functions into
> another, my presentation functions into another, etc... then only including
> the function pages necessary - likely cutting the amount of code being
> parsed in half for any given page.
>
> But then I begin wondering about the speed of making a require() to each of
> these files. maybe three to five requires per page.
>
> Lastly, what about caching or compiling the function libraries so they're
> not being parsed each time?
>
> Any advice on this?
>
>
> - - - - - - -
> - - - -
> WARNING: Some experts believe that use of any keyboard may cause
> serious injury. Consult Users Guide.
>
> [EMAIL PROTECTED]
>
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
