Currently, DPortal CMS have three Smarty Cache Handler Functions:
Caching-on-Files, Memcached, and Caching disabled.
Yesterday, I did
some Caching benchmark, to test the performance with these modes, and the
results (in nanoseconds) are the following:
| 1.- Normal |
2.- copied
100 times |
| Memcached |
0.0887918
0.0782518
0.0918648
0.0890250
0.0847179
---------- |
0.152779
0.132891
0.189441
0.178917
0.174865
--------- |
| 0,086530 |
0,16577 |
|
| 1.- Normal |
2.- copied
100 times |
| Cache
disabled |
0.0694780
0.0797469
0.0685451
0.0851321
0.0830941
----------
|
0.163043
0.130159
0.164993
0.155334
0.143921
--------- |
| 0,077199 |
0,15149 |
|
| 1.- Normal |
2.- copied
100 times |
| Cache
on-files |
0.0766510
0.0782308
0.0925061
0.0841941
0.0825970
----------
|
0.0878369
0.0812170
0.1022429
0.0959160
0.0917348
---------- |
| 0,082835 |
0,091789 |
|
In summary, Caching-on-files has been better performance than Memcache,
considering than the Benchmark has been made in my PC with Linux, when I'm the
only one user, and I've opened the Browser (Iceweasel), and the Desktop
environment. In conclusion, this benchmark does not apply to Servers with lot of
traffic. Benchmarks should be done in all scenarios and most of the
Webservers.
DPortal CMS have a Benchmark mode, that write the Script executed, the
Timestamp and the time of execution. These data may be used to compare the
execution times of every query. Then, you can send me this file to compare them,
and inquire whether if Memcached is better than
Caching-on-Files in a production environment.
Comments