Viewing profile — reconditerose
reconditerose
HN member- Joined
- Tue, Oct 19, 2021, 7:16 AM UTC
- HN karma
- 325
- Public activity
- 68 items
- HN profile
- View on Hacker News ↗
About reconditerose
No profile information was provided.
Recent public activity
- story
-
comment
Comment #45504783
LuaJIT is mostly compatible with 5.1, our goal is to make it pluggable so you can run with either 5.4 or 5.1.
-
comment
Comment #45498027
Seems similar in impact to https://nvd.nist.gov/vuln/detail/cve-2021-32626 , I wonder why this has a CVE 10. This code also looks generally fixed in Lua5.4, https://github.com/lua/…
- story
-
comment
Comment #43862156
Google is well known for having banned AGPL ( https://opensource.google/documentation/reference/thirdparty... ).
-
comment
Comment #43861247
The tl;dr is it's just a lockless hashmap attached to a TCP server with a log. Simple Get/Set operations are highly optimized, so with high batching they are able to efficiently fe…
-
comment
Comment #43861050
> So, you are practically saying you were using, at Amazon, all the BSD code we provided, provide an important part of the code to us? You see how broken such model was? At least s…
-
comment
Comment #43860317
My guess is they are making it up. AWS has no public information, but there are some high profile customers that have migrated https://aws.amazon.com/elasticache/customers/ .
-
comment
Comment #43860299
Do you have data to back up your claims? I see a lot of customer claims for Valkey here, https://aws.amazon.com/elasticache/customers/ . Neither of the AWS or GCP offerings are in …
-
comment
Comment #43860273
The Valkey implementation of multi-threading is fundamentally different than what existed in Redis. The history dates back to work done in ElastiCache that was released as "Enhance…
-
comment
Comment #43860105
It's not just a fork, there have been two releases on Valkey that improved performance and memory efficiency. There is a lie that Redis likes to spread that only their own employee…
-
comment
Comment #43859906
Yeah, there has been a lot of stuff like performance [1] and efficiency improvements [2]. A lot of the contributors, that didn't work for Redis labs but worked on Redis OSS before …
- story
-
comment
Comment #42394004
Everything we do is open-source, so you're free to take it and incorporate it back into Redis. (Although I'm more into rewriting the data structures to more efficient on modern CPU…
-
comment
Comment #42393946
As one of those 12 other people, number of commits is not a good metric in this context. When you have a single maintainer, like antirez was for a long time, he could commit 10+ co…
-
comment
Comment #42381081
I know this doesn't mean much, but I spent a lot of time outside of work helping to maintain the Redis codebase. I attended our meetings and responded to issues on vacation because…
-
comment
Comment #42380006
Valkey maintainer here. ¯\_(ツ)_/¯ I worked with antirez a bit before he left the project in 2020, and I still look fondly back on that time since he was a wonderful person and he h…
-
comment
Comment #42257721
The only public record I've seen him talking about it was in https://github.com/valkey-io/valkey/issues/544 , where he mentioned having sold the copyright.
-
comment
Comment #42207384
There is a lot of adoption of Valkey. I know it's fun to hate on AWS, but there is a wider shift than just them. https://cloud.google.com/blog/products/databases/announcing-... htt…
-
comment
Comment #42207357
We're working on it, you can follow the progress here: https://github.com/valkey-io/valkey/issues/640 .
-
comment
Comment #42207333
It was always, and still is, a license issue. Redis stack had a proprietary license and now Redis has a proprietary license.
-
comment
Comment #41911329
You might be able to get near 100% of Redis performance without a lot of tuning. Redis has a lot of overhead to make it a production ready system like performance counters, safety …
-
comment
Comment #41616238
> Fair point. Was that foreseeable in 2009? A lot of the actions we take now are based on what's reasonably foreseeable in the future. I honestly don't recall. The company now know…
-
comment
Comment #41616121
The other is the company that bought the trademark https://github.com/valkey-io/valkey/issues/54 .
-
comment
Comment #41584813
* Google added support to Valkey: https://cloud.google.com/memorystore * AWS says they are moving: https://aws.amazon.com/blogs/opensource/why-aws-supports-val... * Aiven added Val…