Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DiceDB

dicedb.io

Post reply on HN
Print view View original

41–50 of 143 posts

Re: DiceDB

#41

Post by davekeck »

alexey-salmin wrote: post #36

| Metric | DiceDB | Redis | | -------------------- | -------- | -------- | | Throughput (ops/sec) | 15655 | 12267 | | GET p50 (ms) | 0.227327 | 0.270335 | | GET p90 (ms) | 0.337919 | 0.329727 | | SET p50 (ms) | 0.230399 | 0.272383 | | SET p90 (ms) | 0.339967 | 0.331775 | UPD Nevermind, I didn't have my eyes open. Sorry for the confusion. Something I still fail to understand is where you can actually spend 20ms while…

> Something I still fail to understand is where you can actually spend 20ms

Aren’t these numbers .2 ms, ie 200 microseconds?

Re: DiceDB

#42

Post by Kerbonut »

alexey-salmin wrote: post #36

| Metric | DiceDB | Redis | | -------------------- | -------- | -------- | | Throughput (ops/sec) | 15655 | 12267 | | GET p50 (ms) | 0.227327 | 0.270335 | | GET p90 (ms) | 0.337919 | 0.329727 | | SET p50 (ms) | 0.230399 | 0.272383 | | SET p90 (ms) | 0.339967 | 0.331775 | UPD Nevermind, I didn't have my eyes open. Sorry for the confusion. Something I still fail to understand is where you can actually spend 20ms while…

Looks like your units are in ms, so 0.20 ms.

Re: DiceDB

#43

Post by [deleted] »

alexey-salmin wrote: post #36

| Metric | DiceDB | Redis | | -------------------- | -------- | -------- | | Throughput (ops/sec) | 15655 | 12267 | | GET p50 (ms) | 0.227327 | 0.270335 | | GET p90 (ms) | 0.337919 | 0.329727 | | SET p50 (ms) | 0.230399 | 0.272383 | | SET p90 (ms) | 0.339967 | 0.331775 | UPD Nevermind, I didn't have my eyes open. Sorry for the confusion. Something I still fail to understand is where you can actually spend 20ms while…

[deleted]

Re: DiceDB

#44

Post by [deleted] »

alexey-salmin wrote: post #36

| Metric | DiceDB | Redis | | -------------------- | -------- | -------- | | Throughput (ops/sec) | 15655 | 12267 | | GET p50 (ms) | 0.227327 | 0.270335 | | GET p90 (ms) | 0.337919 | 0.329727 | | SET p50 (ms) | 0.230399 | 0.272383 | | SET p90 (ms) | 0.339967 | 0.331775 | UPD Nevermind, I didn't have my eyes open. Sorry for the confusion. Something I still fail to understand is where you can actually spend 20ms while…

[deleted]

Re: DiceDB

#45

Post by wesselbindt »

jstummbillig wrote: post #40
wesselbindt wrote: post #37

Earlier quoted context omitted.

When I ctrl+F the landing page for key and value, I find nothing. Reading it in full, I also come up empty handed. Which part of the landing page implies it's a key value store?

They did not say anything about key/value in their message.

You are absolutely right, my bad.

Re: DiceDB

#46

Post by esafak »

alexey-salmin wrote: post #36

| Metric | DiceDB | Redis | | -------------------- | -------- | -------- | | Throughput (ops/sec) | 15655 | 12267 | | GET p50 (ms) | 0.227327 | 0.270335 | | GET p90 (ms) | 0.337919 | 0.329727 | | SET p50 (ms) | 0.230399 | 0.272383 | | SET p90 (ms) | 0.339967 | 0.331775 | UPD Nevermind, I didn't have my eyes open. Sorry for the confusion. Something I still fail to understand is where you can actually spend 20ms while…

They also sounded fishy to me. I'd expect closer to 10x as much throughput with Redis: https://redis.io/docs/latest/operate/oss_and_stack/managemen...

Re: DiceDB

#47

Post by hp77 »

ac130kz wrote: post #38

Any reason to use this over Valkey, which is now faster than Redis and community driven? Genuinely interested.

DragonflyDB is also in that race, isn't it?

Re: DiceDB

#48

Post by OutOfHere »

In-memory caches (lacking persistence) shouldn't be called a database. It's not totally incorrect, but it's an abuse of terminology. Why is a Python dictionary not an in-memory key-value database?
Post reply on HN