5 ms·
Running MONITOR in production can severely affect performance, by 50% per monitoring client according to the documentation. twemproxy independently exposes som
by partycoder 10y ago
Running MONITOR in production can severely affect performance, by 50% per monitoring client according to the documentation.
twemproxy independently exposes some statistics, it's probably safer to do it that way.
- kortox 10y agoHi, I'm the author of the post. I'll have to look into getting the metrics from Twemproxy in the future. I typically only run MONITOR for a few seconds 'cause I'm usually just looking for high volume commands & keys.
- antirez 10y agoOP may want to try "INFO commandstats" to get the same metrics in a much cheaper way. Example output: # Commandstats cmdstat_info:calls=1,usec=57,usec_per_call=57.00 cmdstat_cluster:calls=8,usec=211,usec_per_call=26.38 cmdstat_zrange:calls=4,usec=1990,usec_per_call=497.50
- partycoder 10y agoExcellent remark. Note that antirez is Salvatore Sanfilippo, the author of redis. Kudos