If you measure performance impact using CPU performance counters (VTune, oprofile, perf) or even better CPU emulator (callgrind) you'll see slight degradation. It's also clear that it makes some degradation from code review. 1% difference is invisible because measurement mistake is usually bigger and also performance may change from build to build because of different code layout.
Anyway, this is not a stopper, just an issue that would be great to fix. Thanks. Dmtiry. On Tue, Feb 10, 2015 at 11:09 AM, Matt Ficken <themattfic...@gmail.com> wrote: > FYI, the patch doesn't cause a performance regression. > > I built on and tested with IIS/Windows. Performance remains the same for > Wordpress, Symfony and Joomla. Mediawiki actually increased slightly (5%), > so performance is increase/decrease is not an issue here, the language and > engine are. > > > If you're interested, see: > > http://windows.php.net/downloads/snaps/ostc/pftt/perf/results-20150209-master_rcaf5521-scalar_type_hints_2_strict_mode-8436.html > > > Regards > -M > > > On Mon, Feb 9, 2015 at 6:43 PM, Pierre Joye <pierre....@gmail.com> wrote: > > > On Feb 10, 2015 1:22 AM, "Lars Strojny" <l...@strojny.net> wrote: > > > > > > Hi Matteo, > > > > > > sorry for the late response. > > > > > > > On 07 Feb 2015, at 12:46, Matteo Beccati <p...@beccati.com> wrote: > > > > > > > > Maybe it's just me, but I didn't quite understand the point you are > > making here. Are you saying that declares are more or less like ini > > settings? > > > > > > Yes, exactly that. The new declare()-statement will fundamentally > change > > how the engine behaves and one will have two learn more or less two > flavors > > of PHP. Even worse I am forced to use the PHP flavor the person picked > who > > changed the declare() statement last. > > > > No. You are not. > > > > > cu, > > > Lars > > >
