4 ms·
Going from a single processes holding all your data to having your data sharded across multiple processes can be more than a little effort. Also, it might now
by sciurus 7y ago
Going from a single processes holding all your data to having your data sharded across multiple processes can be more than a little effort.
Also, it might now have any benefit for you. Imagine a certain key is particularly hot. Having one multithreaded redis process handling access to it might speed things up. Running multiple sharded redis processes won't, since only one of them will have that key.
- nitwit005 7y agoMost redis users are running multiple instances regardless. That some of them happen to be on the same machine is largely a detail. It would make a little difference if there was a single hot key, but that's a bit unusual. Typically there's some subset of keys that are hot, and you can get them to hash across instances. People also tend to cache those values on the clients, as banging on redis constantly is a waste.
- derefr 7y ago> but that's a bit unusual It's pretty common when using a single Redis stream as a lightweight Kafka.