With the new slotToKey struct, it is possible to start tracking some metrics, such as memory usage (key size + value size but not counting fragmentation) and keyspace_hits, at the slot level. I can see this information being useful for an application to understand the skew in its workload. I wonder what is the best way to expose these metrics? Should it be part INFO or CLUSTER INFO, which would make the output explode though? Or should it be exposed via a new cluster command, CLUSTER GETSLOTINFO <slot_number_1> <slot_number_2> ... <slot_number_n> perhaps? @zuiderkwast @madolson what are your thoughts?
Originally posted by @PingXie in #10411
With the new slotToKey struct, it is possible to start tracking some metrics, such as memory usage (key size + value size but not counting fragmentation) and keyspace_hits, at the slot level. I can see this information being useful for an application to understand the skew in its workload. I wonder what is the best way to expose these metrics? Should it be part
INFOorCLUSTER INFO, which would make the output explode though? Or should it be exposed via a new cluster command,CLUSTER GETSLOTINFO <slot_number_1> <slot_number_2> ... <slot_number_n>perhaps? @zuiderkwast @madolson what are your thoughts?Originally posted by @PingXie in #10411