PHPBench.com was constructed as a way to open people's eyes to the fact that not every PHP code snippet will run at the same speed. You may be surprised at the results that this page generates, but that is ok. This page was also created so that you would be able to find discovery in these statistics and then maybe re-run these tests in your own server environment to play around with this idea yourself, by using the code examples (these code examples are automatically generated and as the code in my .php files change, so do they).

NOTE: You must keep in mind to refresh this page a few times to "catch" the right result. The numbers change sometimes drastically during each refresh. I assume that this is because of PHP's memory garbage collector that drops in randomly and also other processes that run on this machine have an influence.

NOTE: The microtime() method for testing out these tests has only been utilised for simplicities sake. If anything more advanced was used, those whom are just starting out on their PHP journey would have difficulties understanding.

Read Loop:foreach() vs. for() vs. while(list() = each())

What is the best way to loop a hash array?

Given is a Hash array with 100 elements, 24byte key and 10k data per entry

+ 110 %

foreach($aHash as $val);

Total time: 24 µsview code

+ 671 %

while(list(,$val) = each($aHash));

Total time: 147 µsview code

+ 100 %

foreach($aHash as $key => $val);

Total time: 22 µsview code

+ 711 %

while(list($key,$val) = each($aHash));

Total time: 156 µsview code

+ 264 %

foreach($aHash as $key=>$val) $tmp[] = $aHash[$key];

Total time: 58 µsview code

+ 785 %

while(list($key) = each($aHash)) $tmp[] = $aHash[$key];

Total time: 172 µsview code

+ 461 %

Get key-/ value-array: foreach($aHash as $key[]=>$val[]);

Total time: 101 µsview code

+ 265 %

Get key-/ value-array: array_keys() / array_values()

Total time: 58 µsview code

+ 374 %

$key = array_keys($aHash);
$size = sizeOf($key);
for ($i=0; $i<$size; $i++) $tmp[] = $aHash[$key[$i]];

Total time: 82 µsview code

Conclusion:

In all cases I've found that the foreach loop is substantially faster than both the while() and for() loop procedures. One thing to note is that when using an entire loop from the start it's extremely good to use the reset() function in all examples

Given that the previous version of the tests have been very controvercial and incorrect, I must appologise for forgetting to implement the reset() function to allow the while() loops to start from the beginning instead of the end. Thanks to Anthony Bush for spotting this out.

Counting LoopsFor-loop test

Is it worth the effort to calculate the length of the loop in advance?

e.g. "for ($i=0; $i<$size; $i++)" instead of "for ($i=0; $i<sizeOf($x); $i++)"

A loop with 1000 keys with 1 byte values are given.

+ 116 %

With pre calc - count()

Total time: 239 µsview code

+ 52418 %

Without pre calc - count()

Total time: 107978 µsview code

+ 100 %

With pre calc - sizeof()

Total time: 206 µsview code

+ 52390 %

Without pre calc - sizeof()

Total time: 107920 µsview code

Conclusion:

Unsurprising results... this is one of the easiest things to implement in any application and is the widest agreed upon benchmarking item within the online PHP community. The results basically speak for themselves.

Using the =&-ref-operator$obj = new SomeClass() vs. $obj =& new SomeClass()

Is a good idea to use the =&-ref-operator when creating a new object? Call 1'000x

+ 100 %

$obj = new SomeClass();

Total time: 653 µsview code

+ 103 %

$obj =& new SomeClass();

Total time: 672 µsview code

Conclusion:

There seams to be no difference in performance.

Using the =&-ref-operator$obj = $someClass->f() vs. $obj =& $someClass->f()

Is a good idea to use the =&-ref-operator when calling a function in an object? Call 1'000x

+ 100 %

$obj = $someClass->f();

Total time: 608 µsview code

+ 236 %

$obj =& $someClass->f();

Total time: 1438 µsview code

Conclusion:

Unless your extremely worried about how much RAM your using, leaving the &-ref-operator out seems like the slightly faster option.

Quote Typesdouble (") vs. single (') quotes

Is a there a difference in using double (") and single (') quotes for strings. Call 1'000x

+ 160 %

single (') quotes. Just an empty string: $tmp[] = '';

Total time: 479 µsview code

+ 104 %

double (") quotes. Just an empty string: $tmp[] = "";

Total time: 313 µsview code

+ 110 %

single (') quotes. 20 bytes Text : $tmp[] = 'aaaaaaaaaaaaaaaaaaaa';

Total time: 329 µsview code

+ 100 %

double (") quotes. 20 bytes Text : $tmp[] = "aaaaaaaaaaaaaaaaaaaa";

Total time: 300 µsview code

+ 103 %

single (') quotes. 20 bytes Text and 3x a $ : $tmp[] = 'aa $ aaaa $ aaaa $ a';

Total time: 309 µsview code

+ 106 %

double (") quotes. 20 bytes Text and 3x a $ : $tmp[] = "aa $ aaaa $ aaaa $ a";

Total time: 317 µsview code

+ 105 %

double (") quotes. 20 bytes Text and 3x a \$ : $tmp[] = "aa \$ aaaa \$ aaaa \$ a";

Total time: 315 µsview code

Conclusion:

In today's versions of PHP it looks like this argument has been satisfied on both sides of the line. Lets all join together in harmony in this one!

Control Structuresswitch/case/default vs. if/elseif/else

Is a there a difference between switch and if structures?. Call 1'000x

+ 147 %

if and elseif (using ==)

Total time: 210 µsview code

+ 134 %

if, elseif and else (using ==)

Total time: 191 µsview code

+ 100 %

if and elseif (using ===)

Total time: 143 µsview code

+ 106 %

if, elseif and else (using ===)

Total time: 151 µsview code

+ 136 %

switch / case

Total time: 194 µsview code

+ 194 %

switch / case / default

Total time: 278 µsview code

Conclusion:

Using a switch/case or if/elseif is almost the same. Note that the test is unsing === (is exactly equal to) and is slightly faster then using == (is equal to).

String Outputecho vs. print

Is a there a difference between what option you use to output your content?. Called within Output Buffering 1'000x

+ 100 %

echo ''

Total time: 104 µsview code

+ 117 %

print ''

Total time: 122 µsview code

+ 184 %

echo 'aaaaaaaaaaaaaaaaaaaaaaaaaaaa'

Total time: 192 µsview code

+ 185 %

print 'aaaaaaaaaaaaaaaaaaaaaaaaaaaa'

Total time: 193 µsview code

+ 468 %

echo 'aaaaaaa'.'aaaaaaa'.'aaaaaaa'.'aaaaaaa'

Total time: 488 µsview code

+ 517 %

echo 'aaaaaaa','aaaaaaa','aaaaaaa','aaaaaaa'

Total time: 539 µsview code

+ 512 %

print 'aaaaaaa'.'aaaaaaa'.'aaaaaaa'.'aaaaaaa'

Total time: 534 µsview code

+ 526 %

$a = 'aaaaaaa';
echo 'aaaaaaa'.$a.'aaaaaaa'.$a

Total time: 548 µsview code

+ 556 %

$a = 'aaaaaaa';
echo 'aaaaaaa',$a,'aaaaaaa',$a

Total time: 579 µsview code

+ 566 %

$a = 'aaaaaaa';
print 'aaaaaaa'.$a.'aaaaaaa'.$a

Total time: 590 µsview code

+ 528 %

$a = 'aaaaaaa';
echo $a.$a.$a.$a

Total time: 550 µsview code

+ 519 %

$a = 'aaaaaaa';
echo $a,$a,$a,$a

Total time: 541 µsview code

+ 554 %

$a = 'aaaaaaa';
print $a,$a,$a,$a

Total time: 577 µsview code

Conclusion:

In reality the echo and print functions serve the exact purpose and therefore in the backend the exact same code applies. The one small thing to notice is that when using a comma to separate items whilst using the echo function, items run slightly faster.

Modify Loop: foreach() vs. for vs. while(list() = each())

What would happen if we alter the reading loop test to test the results of a loop created to simply alter the data in each of the values in the array?

Given again is a Hash array with 100 elements, 24byte key and 10k data per entry.

+ 1283 %

foreach($aHash as $key=>$val) $aHash[$key] .= "a";

Total time: 887 µsview code

+ 240 %

while(list($key) = each($aHash)) $aHash[$key] .= "a";

Total time: 166 µsview code

+ 100 %

$key = array_keys($aHash);
$size = sizeOf($key);
for ($i=0; $i<$size; $i++) $aHash[$key[$i]] .= "a";

Total time: 69 µsview code

Conclusion:

Proof in this example shows how functionally murderous the foreach() loop can be.

Counting LoopsFor vs. While

Is there an actual difference between counting up between the for loop and the while loop?

+ 113 %

for($i = 0; $i < 1000000; ++$i);

Total time: 76522 µsview code

+ 100 %

$i = 0; while($i < 1000000) ++$i;

Total time: 67647 µsview code

Conclusion:

Well there you have it, the while loop 90% of the time is indeed slightly faster

Using the &-ref-operator...as a so called "alias"

Is a good idea to use the &-ref-operator to substitute (or alias) a complex mutidim-array? . Call 1'000x

E.g. $person = &$aHach["country"]["zip"]["street"]["number"]["name"]

+ 234 %

$alias = $aSingleDimArray[$i]

Total time: 906 µsview code

+ 100 %

$alias = &$aSingleDimArray[$i]

Total time: 388 µsview code

+ 235 %

$alias = $aMultiDimArray[$i]["aaaaa"]["aaaaaaaaaa"]

Total time: 911 µsview code

+ 648 %

$alias = &$aMultiDimArray[$i]["aaaaa"]["aaaaaaaaaa"]

Total time: 2513 µsview code

+ 280 %

$alias = veryMultiDimArray[$i]["a"]["aa"]["aaa"]["aaaa"]["aaaaa"]

Total time: 1086 µsview code

+ 1299 %

$alias = &$veryMultiDimArray[$i]["a"]["aa"]["aaa"]["aaaa"]["aaaaa"]

Total time: 5039 µsview code

Conclusion:

Whilst only using a one dimensional array, it's actually faster to use an alias, but anything larger will result in a performance drop.

Variable Type CheckingisSet() vs. empty() vs. is_array()

What is the performance of isSet() and empty(). Call 2'000x

+ 106 %

isSet() with var that was set

Total time: 211 µsview code

+ 108 %

empty() with var that was set

Total time: 215 µsview code

+ 105 %

isSet() with var that was *not* set

Total time: 209 µsview code

+ 106 %

empty() with var that was *not* set

Total time: 210 µsview code

+ 100 %

isSet() with array-var that was set

Total time: 199 µsview code

+ 101 %

empty() with array-var that was set

Total time: 201 µsview code

+ 100 %

isSet() with array-var that was *not* set

Total time: 199 µsview code

+ 103 %

empty() with array-var that was *not* set

Total time: 204 µsview code

+ 515 %

is_array() of an array

Total time: 1024 µsview code

+ 516 %

is_array() of a string

Total time: 1026 µsview code

+ 1167 %

is_array() of a non set value

Total time: 2321 µsview code

+ 1216 %

isSet() AND is_array() of a non set value

Total time: 2417 µsview code

Conclusion:

isSet() and empty() are identical. So alway check if val is set at all befor using type-checking. E.g. if (isSet($foo) AND is_array($foo))