Re: performance: large includes vs small includes with lots of reads
| From: | Luis Bernardo | Date: | Fri, 08 Oct 2004 02:32:00 +0000 |
| Subject: | Re: performance: large includes vs small includes with lots of reads | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-198921@lists.php.net to get a copy of this message | ||
You may find this useful: http://www.hudzilla.org/php/18_1_0.php
"Hans H. Anderson" <email@hansanderson.com> wrote in message
news:Pine.LNX.4.44.0410071137410.28843-100000@koi.host-servers.info...
> I'm trying to tweak my server a bit and wonder if it is better to have a
large
> include file, say 20-40 kb with 15 user-defined functions, of which maybe
3 or 4
> are used on any given page, or to have each function in it's own file and
> include (disk access/read) them only as needed.
>
> Is it faster/more efficient to read one large file or several smaller
ones?
> It's a RS Linux server with a gig of memory.
>
> I'm also looking at PHP Accelerator and such. Do those store only in
memory
> what the script needs, or does it include all that you require or include
in, as
> well?
>
> Thanks,
> Hans