Am 06.11.2017 um 12:09 schrieb Tony Marston:
wrote in message news:55fb932f-7f61-33eb-1fd9-aa425bc6f...@rhsoft.net...
Am 05.11.2017 um 11:24 schrieb Tony Marston:
wrote in message news:d70cc49d-c397-3f09-d08d-b79b31014...@rhsoft.net...
it depends on the implementation and just beause you say so does not
prove anything and even if you need to measure, optimize and make
decisions based on technical facts - what you do is "mimimi i say"
I have worked on software which provided lots of different options,
which means that you have to keep testing if an option is being used
or not. This is an overhead whether you like it or not.
maybe your implementation was bad
Everybody knows that carrying around code which is either rarely used or
not used at all is an overhead
everybody knows that claims without measure the impact are worthless
it can even happen that due the implementation other code paths which
would not have been touched otherwise may get optimized due refactoring
and the end result can be even faster in general
or why did 5.3, 5.4, 5.5 and 5.6 not speaking about 7.0/7.1 *all*
have new features and where *faster* then the previous version -
frankly you are raising alarm for no reason
Can you prove that each new version was faster? Where is your evidence?
everbody knows that and can benchmark it at any time, but if it makes
you happy that others are doing your homework
https://www.phpclasses.org/blog/post/493-php-performance-evolution.html
interesting that you ignore that now completly
how does that change the fact that your claim "such as it being 64bit
instead of 32bit" is nonsense when most of the benchamrks and
production servers out there are running PHP on x86_64 with 86_64
builds for a decade now?
64bit builds of PHP 5 for Windows were all marked as experimental,
therefore not guaranteed to be as reliable as the 32bit versions. The
"experimental" tag was only removed for PHP 7.
yes, but the majority of production servers is running on Linux,
especially in times where they are mostly virtualized
Just think how much faster and easier to maintain it would be if all
this save-a-few-keystrokes dross had not been added in the first place.
again: unproven claim, but in your own world a hashtable probably is
also not O(1) or you are just not capable to optimize software at all
but then stop claim others aren't too
Everybody knows that carrying around code which is either rarely used or
not used at all is an overhead. That's what the 80-20 rule demonstrates
everybody knows that claims without measure the impact are worthless
it can even happen that due the implementation other code paths which
would not have been touched otherwise may get optimized due refactoring
and the end result can be even faster in general
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
