Actually my experience with optimizations is that 2+2 != 4, but that's besides the point. And it also depends on a lot of other factors. Benchmarks are not easy as they are dependent on many factors.
But in any case, we worked hard from day 1 to really componentize TSRM, Zend and somewhat SAPI so that we get a much more maintainable code base with less dependencies. As it is, the PHP code base is becoming more complex and harder to maintain so we need to try our best to keep good interfaces and separations when possible. Also the ability to reuse these components in other projects although not very common has happened and is an additional benefit to the better design. Thanks Rasmus for reverting for now. I think it's best to keep things as-is but if that really isn't an option (or a local yahoo! patch isn't) then we can think of ways to keep the strict interface but make this work. For example by passing a callback via tsrm_startup(}. Andi > -----Original Message----- > From: Derick Rethans [mailto:[EMAIL PROTECTED] > Sent: Monday, May 28, 2007 8:14 AM > To: Stas Malyshev > Cc: Rasmus Lerdorf; Uwe Schindler; 'PHP Internals' > Subject: Re: [PHP-DEV] TSRM changes broke windows compile > > On Fri, 25 May 2007, Stanislav Malyshev wrote: > > > It's great to have a benchmark, thanks! > > > > > The standard of deviation was rather high though. Over > 10 runs on > > > each the averages were: > > > > > > time: 646 req/sec > > > sapi: 659 req/sec > > > > So it's 2%, not that big a deal... > > I think it is... as all the little bits add up to make things quicker. > > regards, > Derick > > -- > PHP Internals - PHP Runtime Development Mailing List To > unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
