DrJosiah

25 ms·

61.
by DrJosiah 8y ago
For random (and not timespace prefixed) uuids, you can end up hitting more blocks because if locality of reference, if you are using b+trees. If you are using an lsm index, you get blocks of data written at the same time in the index anyway
62.
by DrJosiah 8y ago
Have used this to great results in postgres, mysql, redis, etc.
63.
by DrJosiah 8y ago
I have not found a situation where mongodb has been a better choice than postgresql.
64.
by DrJosiah 8y ago
I worked on adding SSL/TLS because I see it as a need, and I knew that I was losing performance with SSL/TLS unwrapping daemons. Until I finished and started benchmarking, I just didn't know how bad the performance hit was. I
65.
by DrJosiah 8y ago
It is better than the code I actually wrote, I've already switched to it as a base, and have been merging my changes in to my local branch today. :) I look forward to everyone having SSL :)
66.
by DrJosiah 8y ago
Thank you! I didn't catch that when it started.
67.
by DrJosiah 8y ago
In one example test I ran, the SSL/TLS unwrapping daemon used 5x the CPU of Redis itself. And generally, the unwrapping daemons always used more CPU (for the reasons explained in the article). With integrated SSL, you're looking a
68.
by DrJosiah 8y ago
Redis is used as a mission critical tool by companies, whether it wants to be or not. The SSL/TLS changes I was making were going to be easy to merge in for those who were interested. And the fork wasn't just for SSL/TLS; it
69.
by DrJosiah 8y ago
Murky waters with cluster? No. Just being concerned about corporate liability / risk. I might have spent too long working under business folks, as some companies won't consider using open-source software unless there is a vendor t
70.
by DrJosiah 8y ago
It's really good code. I've switched to it and started applying my other changes on top. I wouldn't use my fork for the SSL, I would consider using my future version for the other features that are not yet ready. :P
71.
by DrJosiah 8y ago
You're assuming that changes upstream can't be merged into a fork. But SSL isn't the only thing. Transactions with rollbacks too. Being able to kill a Lua script that has already written. Transactions involving keys spread ac
72.
by DrJosiah 8y ago
Awesome work!
73.
by DrJosiah 8y ago
Other changes that I had been working on weren't going to be merged upstream (already rejected), and though I wasn't going to make any attempts to prevent SSL/TLS from being merge-able (I was actually starting from 4.0.9 for
74.
by DrJosiah 8y ago
Thank you very much, that is the best review I've ever received on my book. As for the story; the clues are there in public if you dig a bit, but aren't all that interesting to anyone.
75.
by DrJosiah 8y ago
Please re-read. It's spiped. Fixed 1k blocks, but otherwise reasonable. But #4855 is going to be merged, and my tests show that #4855 is actually faster than my changes, so ... :) I like not having to be responsible for writing SSL&#x2
76.
by DrJosiah 8y ago
I'm about 99% sure that this will get about < 10 downloads. Heck, I've already switched to PR #4855 code, and am applying my other changes forward on top of it today. I've also got a followup post where I talk about the ne
77.
by DrJosiah 8y ago
This specific fork, yes (has to be renamed). Another fork, perhaps not. Per other threads, I've got more work going in for transactions and other features, some of which Salvatore wasn't even interested in hearing about, let alone
78.
by DrJosiah 8y ago
Because up until I posted, this was the official party line as far as I had been made aware: https://redis.io/topics/encryption And this was the start to several other changes I am in the process of adding, which Salva
79.
by DrJosiah 8y ago
As I was going through setting up HAProxy, I ran into a roadblock that stopped me from testing. I will look into it for the next round.
80.
by DrJosiah 8y ago
Redis is a database. Databases should have encryption over the wire. I was late :P
81.
by DrJosiah 8y ago
I'm sorry that I thought I'd introduce myself before talking about the stuff I've done. Usually gives more weight, and like another poster said, it's also a bit of an in-joke for those who've been to one of my talks
82.
by DrJosiah 8y ago
Not just one thing, multiple things. Transactions, performance improvements, and long-term, more, that rely on Transactions and other parts that Salvatore has expressly stated that he wasn't interested in.
83.
by DrJosiah 8y ago
I didn't know about it until after I'd posted. And the fork wasn't just for SSL, it was for additional features that I'd also been trying to get in for ... years.
84.
Forking Redis Followup(dr-josiah.com)
1 points by DrJosiah 8y ago|0 comments
85.
by DrJosiah 8y ago
I'll be around here and in the similarly named Reddit post, feel free to ask questions.
86.
New Redis Fork with SSL and Transactions(dr-josiah.com)
9 points by DrJosiah 8y ago|3 comments
87.
by DrJosiah 9y ago
Looking at 7574 and Bittorrent's BEP 30, unless I'm missing something, the only part that is resisting the attack mentioned in the source article and what you are replying to, comes from also specifying the total length of the
88.
by DrJosiah 9y ago
archive.is has the article for those coming late and see that it's password protected.
89.
by DrJosiah 9y ago
As a guy who just spent the past summer doing (his 19th year of) Python, (6rd year of) Cython(/Pyrex), and (8th year of) C, picking around PyPy, and writing a couple transpilers; the tools are incredible. And I think you're talkin
90.
Transactions with rollbacks on Redis Cluster
1 points by DrJosiah 9y ago|0 comments

More ›