Re: The INI framework in PHP 4.0
| From: | Zeev Suraski | Date: | Fri, 26 May 2000 18:11:10 +0000 |
| Subject: | Re: The INI framework in PHP 4.0 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-19532@lists.php.net to get a copy of this message | ||
On Fri, 26 May 2000, Sascha Schumann wrote:
> > I haven't looked at the source files for the various modules, but I assume
> > that if the session module wasn't using it, there are probably others. If
> > you're the author of one such module, and especially if your current
> > per-request function implementation looks up the values for the various
> > configurable directives, please take the time to convert it to use the INI
> > framework. This will significantly cut down PHP's startup time.
>
> While I agree that reducing the startup time is a good thing, it is not
> that important as you make it.
>
> Once upon a time, I hacked the lazy-request-startup handler code.
> The basic principle was to execute request startups/shutdowns
> only, if the respective module was used during that request.
> Benchmarks showed no significant speedups related to avoiding all
> startup handlers.
How did you benchmark? I find it hard to believe that 12 hash lookups,
malloc's and memcpy's on every request, don't make a significant
difference. Was that time you checked it after the session module was in
place and with that slow startup?
Remember, this is PURE overhead that's not useful for anything and can be
comlpletely avoided. The marginal gain is huge especially with people who
turn on the PHP engine for all pages.
Zeev
--
Zeev Suraski <zeev@zend.com>
http://www.zend.com/