hulk
fatcache seems no maintenance for many years, you can have a try at https://github.com/bitleak/kvrocks which supports Redis protocol.
hi @amarmudrankit: Fatcache may cause too many orphan sockets, as fatcache didn't close client fd. It was fixed at this pull request (https://github.com/twitter/fatcache/pull/19). Whether you code is the latest version？
这个版本修改了 transaction 字段，所以原生的 metamask 校验无法通过，web3.js 已经同步修改，所以没问题
hi, @axot can you dump the request/server latency from stats? it makes no sense that high latency than the twitter/twemproxy while didn't modify the core flow of proxy forward. the...
Hi @axot , the twemproxy metrics were counter and histogram, you also can find some clues why the twemproxy got high latency if you haven't restarted it. The histogram of...
Unsupport the `redis-sentinel` now, but you can subscribe the redis-sentinel's event, update and reload the twemproxy template
yeah, but not now while we doing other high prior features
Many thanks for @IoCing great contribution, overall is good to me. You can help to resolve the conflict.
Do you mean the disk space usage of key? Kvrocks stores its data in disk instead of the memory, so the memory usage of key is meaningless for Kvrocks.
Thanks for your clarification. It makes sense to export the value size of the specific key, and it should be possible since the RocksDB has a way to get the...