There's opinion about statistics which already implemented (memcache, apc)

I've try to make eAccelerator stats but stucked with uptime and hits ...

Suppose apc and memcache stats are wrong ( total values are per backend not BIN)

Idea to count stats in backend keys (what todo with DB ?)

1) check 'bin_first' key for first request if non then write current time() - store $bin_first
2) uptime = time() - $bin_first
3) sets should be counted in 'bin_set'
4) gets should be counted in 'bin_hit' and 'bin_miss'
5) Other values can be counted from previous

In comments I'll try to post code

CommentFileSizeAuthor
#4 331135-cacherouter.patch21.79 KBnick_vh

Comments

andypost’s picture

Same way it's possible provide statistics for fast page cache

andypost’s picture

apache uptime http://bugs.php.net/bug.php?id=31391

Suppose there's no clean solution

slantview’s picture

I got some ideas for this now, and I am going to be implementing them soon. Keep an eye out.

nick_vh’s picture

Title: Statistics » Statistics + admin section work
Assigned: Unassigned » nick_vh
StatusFileSize
new21.79 KB

During Drupalcon DC I took quite some time to figure out cacherouter and its statistics.

I made some statistics available for the DB mode and planning to do more for the other engines.

So what changed?
- added stats function in the base class
- added first cache item/ last cache item
- implemented memory in use by cache (in KB)
- implemented memory available (extra disk parameters)
- implemented how many sets
- some overall statistics smalltalk
- fixed whitescreen in admin (theme issue thanks to John Van Dyk, don't know his nickname altough he's a famous guy :) )

If you guys have any questions or comments, shoot!

nick_vh’s picture

And we should seriously think about the effects of some statistics we would like to implement. This is not possible for all the engines and the way it's implemented now is not flexible enough to give more engine specific details.

Would like to see more seperated details.

andypost’s picture

Why not implement internal data structures (maybe in apc xcache eacc if avail) to count hits|misses

TripleEmcoder’s picture

Subscribing.

nick_vh’s picture

Is there any update on this. Is this still required? Did not follow cacherouter for a while but I am willing to do something about it if somebody wants to write a roadmap about what is necessary?

andypost’s picture

Statistics now live in different module #760056: Steal this module - Cache Router Statistics