pushkarg

4 ms·

1.
by pushkarg 3y ago
The benchmark highlights the value prop to the end user who can now use a "local program" ie an embedded database and get the perf wins over Redis - without worrying about data management (backups/replication/what-not).
2.
by pushkarg 3y ago
I just explained how implementing the Redis protocol will inherit inefficiencies of Redis in IKV - so I don't understand how the comparison will be fair or honest. Hope this addresses your original question about why we wrote a custom
3.
by pushkarg 3y ago
Point taken. Not opposed to self-hosting, its just that we haven't seen interest in that so far. And the way things are right now, it can be very complex to setup.
4.
by pushkarg 3y ago
Exactly! Accessing data in RAM will be orders of magnitude faster than over the network (maybe this is a good sanity check of our benchmark numbers). The core principle behind IKV is that it allows you to access (large) data-sets without ne
5.
by pushkarg 3y ago
Correct, we are super early so there is no self-serve yet. The primary usecase for this is serving features for ML inference (since eventual consistency is ok and sacrificing write latency for reads is a fair tradeoff). Right now, this is d
6.
by pushkarg 3y ago
Its a managed embedded-store, ie someone can write data, forget about it, come back in a month with new hardware and still access all their data. You can't do that with a traditional embedded store (ex. rocksdb or a local redis instanc
7.
by pushkarg 3y ago
All benchmark details are linked in the Github readme. https://docs.google.com/document/d/1aDsS0V-AybpvXEwblBlahGLp... For Redis - The benchmark client and remote server (ie AWS ElastiCache) were in the same AWS a
8.
by pushkarg 3y ago
IKV is a managed DB solution ex. a user does not need to build data replication or backup pipelines. A "local" Redis instance is not fully managed - the instance goes down - your data is unavailable (unless you build a full distri
9.
by pushkarg 3y ago
Fully-managed; Eventually consistent; Embedded (no RPC for read-path); In-memory with option to spill to disk. Detailed benchmarks linked in the Github Readme. Single digit microsecond read latencies. Written in Rust - available for use in
10.
IKV: embedded key-value store, 100x faster than Redis(github.com)
12 points by pushkarg 3y ago|23 comments