Ping Xie

> As we don't have any data points for Redis Modules, one can't be sure which API(s) were really used. We can argue the opposite way too without concrete data...

>This Module supports every Bloom Filter command (from ReBloom) except for the BF.LOADCHUNK and BF.SCANDUMP and the commands have been implemented with ReBloom compatibility. The reason for not implementing the...

>I think this would be a nice module to start with and help set the baseline for other modules in the future. +1. I am in favor of accepting this...

>With this filtering option introduced, does CLUSTER SHARDS command have any significance in itself? Not sure if I understand your question. Can you elaborate? >@barshaul Regarding removing replica(s) from response...

> The error was basically that we were doing a 4 byte write, starting at byte offset 8, for the first addition to listpack that was of size 10. Practically...

No worries. These can all be addressed incrementally.

@panjf2000, do you mind counting the number of `kevent` calls before and after this change for a given workload (`./valkey-benchmark -r 10000000 -d 1024 -n 10000000 -P 100 -t get,lpop,rpop,spop,zpopmin...

> @valkey-io/core-team Since @PingXie mentioned in the other thread about this, I thought it would be good to try to get consensus on this change. The tl;dr is that in...

I see the value in cross-slot operations within a single-shard setup, and it seems to provide a seamless experience for the client application. However, I'm unclear on how cross-slot operations...

+1. I agree this is a very valid "management" problem to solve. @hwware I think we should also consider the impact of NAT when it comes to the detailed design....