Joe,
I believe that the concept of the Zend Cache shows the contrary. It
basically pre-parses scripts and stores them in memory. Zend.com give
figures up to 603% performance increase
(http://www.zend.com/cguidemo/benchmark_frame.html). Part of this
certainly is due to less disk access, the other part is the time that is
saved in parsing the scripts. So, for a heavily-used application, the
overhead in parsing code that is not needed is all but minimal.
Ben
Joe Stump wrote:
>
> Declaring the functions is minimal. Either your ISP has the memory allocations
> set unbearably low or you aren't coding things very well ...
>
> --Joe
>
> On Thu, Feb 15, 2001 at 04:16:22AM +0100, Ben Peter wrote:
> > Hi Joe,
> >
> > the reason I changed to 'include on demand' was a rather large
> > application which would not work, as the memory limit that my isp had
> > set wouldn't suffice.
> >
> > I have files that are included all the way, yes: DB connection, some
> > common helpers, etc. But I would not include files that the current
> > state of an application (or part of the site) does not need to keep
> > things small.
> > This is especially true for some classes which before included both user
> > access and 'admin' function (for, say, user authentication and
> > administration). I split all of these up into two classes, so that the
> > part that is accessed when a regular user hits the site is minimal, and
> > the administrative functions won't be loaded in that case.
> >
> > Ben
--
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]
