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

GhostDB – A Fast Distributed Cache

github.com

Post reply on HN
Print view View original

11–20 of 37 posts

Re: GhostDB – A Fast Distributed Cache

#11

Post by mbreese »

matt_f wrote: post #9

Could anyone explain a use case for this? (Distributed KV store) Genuine question, thanks

I would imagine instances where you'd use memcached.

Session storage could be one use-case. Another could be caching DB query results for a specified amount of time (1 min, 5 min, etc).

Re: GhostDB – A Fast Distributed Cache

#12

Post by 65536 »

dallbee wrote: post #10
trishume wrote: post #7

“microsecond performance” irks me because you can’t get latencies of a microsecond without very expensive special network cards and APIs which they don’t seem to mention and I doubt they use. So they either mean 10s to hundreds of microseconds or they’re taking the reciprocal of their throughput which would be weird and misleading. If you’ve made a fast product that’s great! Show us with well-explained benchmarks not…

Or, perhaps, they're taking the non-networked use case.

I don’t have a stake in this but the page does say

> delivers microsecond performance at any scale

and then

> a very large hash table that is distributed across multiple machines

So the way that I read it, the network will be involved when they said “at any scale”.

Re: GhostDB – A Fast Distributed Cache

#13

Post by dvirsky »

Written in Go? I wonder what the GC pressure is going to look like with many small keys. I've written a redis clone in Go a few years ago and the GC pauses when reaching a few GBs of utilization were awful. Granted the Go GC has improved considerably since but it's still going to be noticeable I bet.

Re: GhostDB – A Fast Distributed Cache

#15

Post by mesaframe »

> in-memory, general purpose key-value caching

> GhostDB can provide you with up to a 25x increase in data retrieval speeds when compared to databases such as MongoDB and MySQL.

Isn't it insincere to say your tech is faster than a DBMS which works on a slower hardware.

Re: GhostDB – A Fast Distributed Cache

#16

Post by jldugger »

dvirsky wrote: post #13

Written in Go? I wonder what the GC pressure is going to look like with many small keys. I've written a redis clone in Go a few years ago and the GC pauses when reaching a few GBs of utilization were awful. Granted the Go GC has improved considerably since but it's still going to be noticeable I bet.

> I've written a redis clone in Go a few years ago and the GC pauses when reaching a few GBs of utilization were awful.

Probably managable with a good slab allocator.

Re: GhostDB – A Fast Distributed Cache

#18

Post by rawoke083600 »

Congrats for getting it out there ! That is more than half the battle. I thing I would like to see also is more Redis-Clones. The redis-parts not the KV parts(lots of options here). I want some alternatives or speed improvements for "Unions" and other set based operations :). PS. GhostDB looks cool !

Re: GhostDB – A Fast Distributed Cache

#20

Post by dvirsky »

jldugger wrote: post #16
dvirsky wrote: post #13

Written in Go? I wonder what the GC pressure is going to look like with many small keys. I've written a redis clone in Go a few years ago and the GC pauses when reaching a few GBs of utilization were awful. Granted the Go GC has improved considerably since but it's still going to be noticeable I bet.

> I've written a redis clone in Go a few years ago and the GC pauses when reaching a few GBs of utilization were awful. Probably managable with a good slab allocator.

Yeah, I've seen people do that but I've glanced the code, it's certainly not the case here.
Post reply on HN