The statements that Redis doesn’t need multi-threading because generally Redis is not CPU bound it’s network bound is utter total bullshit. I’ve benchmarked it. It cannot realize full network capacity with its current single threaded design.
Throwing away density for convenience is ok as long as it's an economic time/value/SLI call - for many systems/businesses it's the right call. The corollary also holds true. For Redis, license instability is a bigger adoption barrier today though...
-
-
Core Redis is BSD licensed, and it has a diverse base of copyright holders (including non Redis Labs employees) so re-licencing would take effort and individuals signing off. So let's clear the FUD?
-
True and acknowledged, and I'm conflicted ... but the latest licensing trend is a pair-programming with a lawyer shitshow I just don't want to visit again ...
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.