Viewing profile — mehrant

5 years ago, I made a derivative of SAP-1 (mainly inspired by Ben Eater) on breadboard with few improvement and called it MSAP-1 ( https://github.com/mehrantsi/MSAP-1 ) I made my o…

Feel free to test for yourself :) Test was done using Redis benchmark for 1M random keys, 50 clients, Pipeline depth, 64. I did this locally on my MBP M3-Max. This gives a little o…

The Redis-compatible server is based on Feox DB, which is an embedded KV Store in Rust. https://github.com/mehrantsi/feoxdb

After the release of Feox DB ( https://github.com/mehrantsi/feoxdb ), I received a number of questions/requests about a potential service layer on top. I spent the last week and cr…

When operations complete in 200ns instead of blocking for microseconds/milliseconds on fsync, you avoid thread pool exhaustion and connection queueing. Each sync operation blocks t…

Thanks for the comment. :) The target use cases include: 1- Session stores (can be reconstructed from auth service) 2- leaderboards/counters (recent scores/counters can be recalcul…

Thanks! yeah, SQLite's write lock is painful for concurrent apps. I'm comfortable with kernel development, so I brought some of those patterns here - RCU-style lock-free reads, per…

Reading your comment about comparing the throughput to Redis, it seems to me that you haven't read the benchmark article really. In there, we're in fact comparing the "throughput" …

One thing we'd like to know your opinion on, is our key monitoring via WebSocket (pub-sub) feature. You can read more about it in our documentation under WebSocket. Is it something…

Thank you for your thoughtful critique. To clarify what our numbers actually mean and address your main question of "what does that number actually mean": 1- The 600ns figure repre…

for the time being, have a look at this please: http://hpkv.io/videos/performance_local.webm this is 1M records, 3M operations on a single node, single thread, recorded in real tim…

our p50 is indeed 600ns for write, the way I explained it. I understand that at this point, this can be read as "trust me bro" kind of statement, but I can offer you something. we …

thanks for the feedback :) our main target for "performance" value proposition are companies and businesses which will setup HPKV either locally (Enterprise plan) for nanosecond pe…

thank you :) it would be interesting to have a chat for sure. would you mind dropping an email on the email I mentioned in OP and I'll reach out to you.

your concern is understandable. we'll be in touch :)

We provide some elements of ACID guarantees, but not full ACID compliance as traditionally defined in database systems: Atomicity: Yes, for individual operations. Each key-value op…

of course. the speeds down to 15us can be achieved over network over our custom protocol on the same region. for sub-microsecond latency, you need to have HPKV running on the same …

sure! :)

yes, in that case data can potentially be lost. 30 sec in a worse case scenario without HA.

sorry for not being clear again. by saying this number does not represent full fsync operation, I meant it doesn't include the SSD write time. this is the time to update KVs intern…