4 ms·
Somehow no one has mentioned KeyDB so: https://github.com/Snapchat/KeyDB https://github.com/Snapchat/KeyDB [EDIT] whoops, didn't read the article, went immedi
by hardwaresofton 3y ago
Somehow no one has mentioned KeyDB so:
https://github.com/Snapchat/KeyDB https://github.com/Snapchat/KeyDB
[EDIT] whoops, didn't read the article, went immediately to comments for recommendations since that's what HN is good at IMO.
- manacit 3y agoIt's mentioned in the first paragraph of the article, and "KeyDB" is featured 14 more times throughout the rest of it.
- Signez 3y agoWell, it's talked about lenghtly in the article.
- secondcoming 3y agoKeyDB is flaky garbage
- hardwaresofton 3y agoWhoaaaa I’d love some details on this reaction, do you have any stories or anecdotes to share? I have to say I’ve never hit its limits so I’ve never lost trust in it
- secondcoming 3y agohttps://news.ycombinator.com/threads?id=secondcoming#39865664 https://news.ycombinator.com/threads?id=secondcoming#3986566...
- pimsn3000 3y agoPlease explain
- secondcoming 3y agoWe got hit by [0] and so had to pin to an older version (we didn't raise the issue). Also, just look at the amount of open bugs and their age [1] They also recommend using swap for some reason, however if your memory usage reaches the point where swap is being used the performance is so bad that the machine may as well be dead. It's been nothing but trouble, which is a shame because the changes they've done to redis have crossed my mind too. We'll probably move to Scylla. [0] https://github.com/Snapchat/KeyDB/issues/465 https://github.com/Snapchat/KeyDB/issues/465 [1] https://github.com/Snapchat/KeyDB/issues https://github.com/Snapchat/KeyDB/issues