That page is not very informative. It doesn't explain why anyone should be interested in this project, and compare with alternatives. What's the novelty, what's the edge, etc.
Hardly surprising that it didn't gain much traction.
The Kivaloo Data Store
21–30 of 78 posts
Re: The Kivaloo Data Store
#22Earlier quoted context omitted.
Well yeah but the GPG key is also served insecurely: http://www.tarsnap.com/tarsnap-signing-key-2020.asc
... you know you can change that URL to start "https" if you like?
Of course you are right, but some commonly accepted procedure nowadays is to do that automatically with a redirect, as a service for the user. Sure, you may have a reason for not to do so, but instead of dismissing a valid argument you could maybe explain why not ...
Edit: On second thought, I recognize this whole subthread started with the wrong tone ("ironic", "reckless"), kind of dismissive or patronizing and not calling for a constructive discussion, so please disregard this comment of mine, sorry.
Re: The Kivaloo Data Store
#23Note: The performance values mentioned on that page (on an EC2 c1.medium instance using spinning-rust disks!) is wildly out of date. I'll get around to updating them some day. For reference, on my laptop (Dell Latitude 7390 with an i7-8650U CPU): * Bulk inserts run at ~600,000/second (up from 125,000). * Bulk extracts run at ~660,000/second while in RAM (up from 30,000) and ~220,000/second from disk (up from 20,000).…
Have you ever considered getting a Jepsen test done for kivaloo? The claims re: durability and linearizability are worth proving out that way
Re: The Kivaloo Data Store
#24I was looking at this yesterday because of the post on "use of a life" post by cperciva. One thing on the benchmarks was I didn't know what was considered "good" numbers, even though I know it's dependent on the type of workload.
Is there a way to compare it to other key-value stores in a fair apples to apples comparison?
Re: The Kivaloo Data Store
#25Note: The performance values mentioned on that page (on an EC2 c1.medium instance using spinning-rust disks!) is wildly out of date. I'll get around to updating them some day. For reference, on my laptop (Dell Latitude 7390 with an i7-8650U CPU): * Bulk inserts run at ~600,000/second (up from 125,000). * Bulk extracts run at ~660,000/second while in RAM (up from 30,000) and ~220,000/second from disk (up from 20,000).…
Have you ever considered getting a Jepsen test done for kivaloo? The claims re: durability and linearizability are worth proving out that way
I am genuinely intrigued about how much is costs to commission those tests. They are so complete and thorough that I can't see myself being able to afford one for some project of mine, but I would absolutely like to to have an estimate
Re: The Kivaloo Data Store
#26Is there somewhere I can nominate kivaloo for some sort of easily understandable code award? Granted I'm a little biased as it looks a lot like code I would write myself, but wow, it's so refreshing to see code that's full of (useful! illuminating!) comments. Thanks cperciva!
Re: The Kivaloo Data Store
#27Earlier quoted context omitted.
Have you ever considered getting a Jepsen test done for kivaloo? The claims re: durability and linearizability are worth proving out that way
I am genuinely intrigued about how much is costs to commission those tests. They are so complete and thorough that I can't see myself being able to afford one for some project of mine, but I would absolutely like to to have an estimate
Jepsen's website says you can contact Kyle at aphyr [at] jepsen [dot] io for pricing.
Re: The Kivaloo Data Store
#28Last release 2011-10-11? Interesting that the author is here commenting as well on a 9 year old project.
I didn't bother doing releases for a while, since nobody else (AFAIK) was using the code.
No worries there, I was just wondering out loud why OP posted, and how you found the thread so quickly
Re: The Kivaloo Data Store
#29Earlier quoted context omitted.
Have you ever considered getting a Jepsen test done for kivaloo? The claims re: durability and linearizability are worth proving out that way
I am genuinely intrigued about how much is costs to commission those tests. They are so complete and thorough that I can't see myself being able to afford one for some project of mine, but I would absolutely like to to have an estimate
Also, if you're willing to just write the tests yourself, Jepsen is open-source and Kyle Kingsbury offers a tutorial on how to use it on GitHub.
You might not get the same level of sophistication right away, of course, but that's just a matter of time and diligence.
Re: The Kivaloo Data Store
#30Earlier quoted context omitted.
I didn't bother doing releases for a while, since nobody else (AFAIK) was using the code.
No worries there, I was just wondering out loud why OP posted, and how you found the thread so quickly
Paul Graham tweeted yesterday[1] an essay that the author had written which references kivaloo. At least, that's how I came to know about it yesterday.
I read the document on it, then tried to imagine what I would use it for, and couldn't really come up with a use case. I had trouble understanding where I would apply the 255 byte key to 255 byte value paradigm. I also didn't know how the benchmarks compared to similar applications.