Faster – Fast key-value store from Microsoft Research
1–10 of 84 posts
Re: Faster – Fast key-value store from Microsoft Research
#2But is it faster than Aerospike or Tarantool?
Re: Faster – Fast key-value store from Microsoft Research
#3"What differentiates FASTER are its cache-optimized index that achieves very high performance — up to 160 million operations per second when data fits in memory;"
I really dislike when papers make performance claims like this in the introduction. That "160 million" number is so meaningless at face value because everything from the runtime environment to the hardware is going to play a huge role in ops. I rather see how it compares against other key-value stores across a number of configurations and use cases.
Re: Faster – Fast key-value store from Microsoft Research
#4"What differentiates FASTER are its cache-optimized index that achieves very high performance — up to 160 million operations per second when data fits in memory;" I really dislike when papers make performance claims like this in the introduction. That "160 million" number is so meaningless at face value because everything from the runtime environment to the hardware is going to play a huge role in ops. I rather see h…
Agreed. Hardware and software has had a fair amount of upgrades since then, but reading that I could pseudo-remember that quote by the memcache guy that goes something like "you can't tell if that or that tweak is giving you a few % more requests because you're being i/o limited by your network link anyway".
Re: Faster – Fast key-value store from Microsoft Research
#5But is it faster than Aerospike or Tarantool?
Is it webscale?
Re: Faster – Fast key-value store from Microsoft Research
#6It would be nice to know why I would use this instead of something tried and tested like Redis, but the sparse description doesn't really help.
Re: Faster – Fast key-value store from Microsoft Research
#7For those wondering what this is, it is not a client/server app, from what I can tell, but an embedded engine. It looks like it's intended to be a library, and it's been implemented in two languages (C# and C++).
To get something like Redis or Riak you would have to build API, clustering, etc. on top of it. So it's more analogous to libraries like RocksDB, BoltDB, BDB etc.
Paper: https://www.microsoft.com/en-us/research/uploads/prod/2018/0...
Re: Faster – Fast key-value store from Microsoft Research
#8"What differentiates FASTER are its cache-optimized index that achieves very high performance — up to 160 million operations per second when data fits in memory;" I really dislike when papers make performance claims like this in the introduction. That "160 million" number is so meaningless at face value because everything from the runtime environment to the hardware is going to play a huge role in ops. I rather see h…
It'd be awesome if they provided a comparison of other tools on the same hardware like, "on an AWS M4.xlarge instance we were able to achieve 160m/ops/sec when the dataset fit into memory where as redis only did X"
Lacking that I agree it's a pretty meaningless stat.
Re: Faster – Fast key-value store from Microsoft Research
#9"What differentiates FASTER are its cache-optimized index that achieves very high performance — up to 160 million operations per second when data fits in memory;" I really dislike when papers make performance claims like this in the introduction. That "160 million" number is so meaningless at face value because everything from the runtime environment to the hardware is going to play a huge role in ops. I rather see h…
Links to 'our website' on the github page follows through to this paper [1]. Haven't read through it, but I did see a graph comparing Intel TBB, RocksDB and Masstree.
[1] https://www.microsoft.com/en-us/research/uploads/prod/2018/0...
Re: Faster – Fast key-value store from Microsoft Research
#10Faster than the leading brand