One of the long term things we want to address in Redis is lack of tools to analyze the dataset directly available in the Redis distribution, as first class citizens.
There are a few like redis-cli --latency, or redis-key --bigkeys (I encourage you to try both if you never did it before), but more are needed in order to profile memory, big keys, pretty-print the Slow Log output, and so forth.
The availability of external tools is surely of a great help, but I hope that in the long run we'll have the most important things integrated into redis-cli directly.
I think a viable design would be to put into redis-cli only things that are network oriented, so we should actually merge the functionality of your current tool into redis-check-rdb, that should be renamed just redis-rdb, with the following features:
1) Everything redis-rdb-tools is currently able to do.
2) Sanity checks of RDB files, like redis-check-rdb is doing already.
Makes sense? Thanks again, this would be very very appreciated.
Comments
One of the long term things we want to address in Redis is lack of tools to analyze the dataset directly available in the Redis distribution, as first class citizens.
There are a few like redis-cli --latency, or redis-key --bigkeys (I encourage you to try both if you never did it before), but more are needed in order to profile memory, big keys, pretty-print the Slow Log output, and so forth.
The availability of external tools is surely of a great help, but I hope that in the long run we'll have the most important things integrated into redis-cli directly.
antirez - Author of redis-rdb-tools here. Would you be interested in a patch that adds profiling support to redis-cli?
My approach is to parse the rdb file so that the running server isn't affected. It approximates memory usage, but is fairly representative.
Thanks ksri, that would be very welcomed.
I think a viable design would be to put into redis-cli only things that are network oriented, so we should actually merge the functionality of your current tool into redis-check-rdb, that should be renamed just redis-rdb, with the following features:
1) Everything redis-rdb-tools is currently able to do.
2) Sanity checks of RDB files, like redis-check-rdb is doing already.
Makes sense? Thanks again, this would be very very appreciated.
Definitely makes sense! I'll start looking into this.