Hi guys,
I've been looking at the new cache in 2.0. Does it actually work?
cache on:
jupiter:/sixpack/www# mysqladmin status
Uptime: 3550 Threads: 1 Questions: 3452 Slow queries: 0 Opens: 0
Flush tables: 1 Open tables: 31 Queries per second avg: 0.972
jupiter:/sixpack/www# mysqladmin status
Uptime: 3555 Threads: 1 Questions: 3484 Slow queries: 0 Opens: 0
Flush tables: 1 Open tables: 31 Queries per second avg: 0.980
cache off:
jupiter:/sixpack/www# mysqladmin status
Uptime: 3579 Threads: 1 Questions: 3518 Slow queries: 0 Opens: 0
Flush tables: 1 Open tables: 31 Queries per second avg: 0.983
jupiter:/sixpack/www# mysqladmin status
Uptime: 3584 Threads: 1 Questions: 3550 Slow queries: 0 Opens: 0
Flush tables: 1 Open tables: 31 Queries per second avg: 0.991
Its on a privately hosted system that I'm using to develop some WP
hacks on so I know nobody else is hitting the DB.
I used:
define('ENABLE_CACHE', false);
to make sure it was disabled and
define('ENABLE_CACHE', true);
to make sure it was enabled.
Its definitely creating cache files. In fact, setting ENABLE_CACHE to
false seems to still create cache files ...
I think that I should be able to do better than:
Requests per second: 3.78 [#/sec] (mean)
Time per request: 264.632 [ms] (mean)
Time per request: 264.632 [ms] (mean, across all concurrent
requests)
Transfer rate: 50.75 [Kbytes/sec] received
Is this a bug, or am I just expecting too much? Is there any way I
can verify that it is working as advertised?
Cheers,
Nathan.