Anna: A Fast, Scalable, Flexibly Consistent Key-Value Store

Post by naasking » Sat, Mar 10, 2018, 1:06 AM UTC

nicpottier wrote: post #49

ricardobeat wrote: post #32

Earlier quoted context omitted.

The comparison with Redis is on page 10, and (obviously) takes into account the number of threads. It is a bit presumptuous to post a comment like this without minimal effort, please don’t. Regarding embedded processing, it’s very easy to embed whatever single-threaded language you’d like into C: Lua, Javascript or something new like Gravity. This is orthogonal to the storage / network architecture. A better argument…

The comparison to Redis is in the 4th paragraph of the linked article. "The paper includes numbers showing it beating Redis by over 10x on a single AWS instance" I'm sorry I didn't go read the original paper, but I thought reading the article qualified me to comment. Sorry dad. I think you also misunderstood my point about Lua. Embedded Lua in Redis is so powerful BECAUSE it is single threaded, not because it is just…

Post by nicpottier » Sat, Mar 10, 2018, 1:26 AM UTC

naasking wrote: post #51

nicpottier wrote: post #49

Earlier quoted context omitted.

The comparison to Redis is in the 4th paragraph of the linked article. "The paper includes numbers showing it beating Redis by over 10x on a single AWS instance" I'm sorry I didn't go read the original paper, but I thought reading the article qualified me to comment. Sorry dad. I think you also misunderstood my point about Lua. Embedded Lua in Redis is so powerful BECAUSE it is single threaded, not because it is just…

> "The paper includes numbers showing it beating Redis by over 10x on a single AWS instance" Right single core against single core,the best scenario for Redis, and Anna's an order of magnitude faster. I'm not sure what you don't find impressive about this.

Post by nogenerics123 » Sat, Mar 10, 2018, 2:41 AM UTC

Post by petre » Sat, Mar 10, 2018, 6:27 AM UTC

xstartup wrote: post #11

ralusek wrote: post #5

I feel like between Redis, S3, Cloud Storage, RocksDB, Cassandra, etc...this area strikes me as one that has been solved as well as we could reasonably expect it to be. What the world of data needs more of is continued development into novel indexing strategies/implementations. ElasticSearch, Postgres's GIN index on JSONB, MapReduce, graph databases. I don't need another key value store...

Cassandra is JVM GC issues Redis is in-memory only Cloud Storage - Not sure, how we can use it outside of cloud vendors RocksDB - Facebook just outsourced the engine to the community, where is the service which adds replication, clustering and network interface on top of it? I am sure, they use one internally, why is it not being open-sourced? There is also badger but most of these only offer low-level operation. Sor…

Post by dwenzek » Sat, Mar 10, 2018, 8:36 AM UTC

dwenzek wrote: post #58

dnautics wrote: post #43

Earlier quoted context omitted.

I wonder what the performance would be like if instead of running on ruby they ran it on a scalable virtual machine with near-first-class actors (not truly first class, but the engine is optimized to handle them, and the constructs are extremely important in the standard library) like BEAM.

While Bloom was indeed coded in ruby, they use C++ for Anna: > We get this rich consistency in Anna with a very clean codebase, by porting design patterns of monotone lattice composition from Bloom to C++. In the paper: > The Anna actor and client proxy are implemented entirely in C++. The codebase—including the lattice library, all the consistency levels, the server code, and client proxy code— amounts to about 2000…