Hi all,
I decided to run my standard phpMyAdmin test without APC enabled and got
startling results from siege:
Date & Time, Trans, Elap Time, Data Trans, Resp Time, Trans
Rate, Throughput, Concurrent, OKAY, Failed
2008-06-20 02:02:35, 915, 60.01, 1, 0.98,
15.25, 0.02, 14.88, 915, 0 <-- phpMyAdmin on disk
2008-06-20 02:05:04, 911, 60.04, 1, 0.98,
15.17, 0.02, 14.86, 911, 0 <-- phpMyAdmin in phar
with phar.cache_list
That's right - they are identical in performance. With APC, there is a
performance difference (I'm not sure why, to be honest, this one is
really hard to profile):
Date & Time, Trans, Elap Time, Data Trans, Resp Time, Trans
Rate, Throughput, Concurrent, OKAY, Failed
2008-06-20 01:34:00, 2735, 59.72, 5, 0.33,
45.80, 0.08, 14.95, 2735, 0 <-- phpMyAdmin on disk
2008-06-20 01:36:11, 2409, 60.14, 5, 0.37,
40.06, 0.08, 14.95, 2409, 0 <-- phpMyAdmin in phar
with phar.cache_list
However, the difference is negligible. Thanks to Gopal for the
mini-tutorial on using copy-on-write to implement phar.cache_list, and
kcachegrind for finding the obvious bottlenecks.
Greg
Greg,
Congrats, those are rather impressive results.
Hi all,
I decided to run my standard phpMyAdmin test without APC enabled and
got
startling results from siege:Date & Time, Trans, Elap Time, Data Trans, Resp Time, TransRate, Throughput, Concurrent, OKAY, Failed
2008-06-20 02:02:35, 915, 60.01, 1, 0.98,
15.25, 0.02, 14.88, 915, 0 <-- phpMyAdmin on
disk
2008-06-20 02:05:04, 911, 60.04, 1, 0.98,
15.17, 0.02, 14.86, 911, 0 <-- phpMyAdmin in
phar
with phar.cache_listThat's right - they are identical in performance. With APC, there
is a
performance difference (I'm not sure why, to be honest, this one is
really hard to profile):Date & Time, Trans, Elap Time, Data Trans, Resp Time, TransRate, Throughput, Concurrent, OKAY, Failed
2008-06-20 01:34:00, 2735, 59.72, 5, 0.33,
45.80, 0.08, 14.95, 2735, 0 <-- phpMyAdmin on
disk
2008-06-20 01:36:11, 2409, 60.14, 5, 0.37,
40.06, 0.08, 14.95, 2409, 0 <-- phpMyAdmin in
phar
with phar.cache_listHowever, the difference is negligible. Thanks to Gopal for the
mini-tutorial on using copy-on-write to implement phar.cache_list, and
kcachegrind for finding the obvious bottlenecks.Greg
--
Ilia Alshanetsky