reconditerose

6 ms·

1.
Valkey 9.0 now supports 1B RPS, hash field expiration, and more(valkey.io)
9 points by reconditerose 11mo ago|4 comments
2.
by reconditerose 1y ago
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.
3.
by reconditerose 1y ago
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/lua/blam
4.
Valkey Turns One: How the Community Fork Left Redis in the Dust(gomomentodev.wpenginepowered.com)
11 points by reconditerose 1y ago|0 comments
5.
by reconditerose 1y ago
Google is well known for having banned AGPL ( https://opensource.google/documentation/reference/thirdparty... ).
6.
by reconditerose 1y ago
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 fetch a lot of data efficiently. The architectures s
7.
by reconditerose 1y ago
> 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 stop defending it. I'm not defending it, I'm try
8.
by reconditerose 1y ago
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/ .
9.
by reconditerose 1y ago
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 preview.
10.
by reconditerose 1y ago
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 "Enhanced IO", https://aws.amazon.com/abou
11.
by reconditerose 1y ago
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 employees were working on the core engine at the time of the fo
12.
by reconditerose 1y ago
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 the fork, moved to Valkey and they continued to contrib
13.
Valkey (The Fork of Redis) built a modern hash table to save memory(valkey.io)
5 points by reconditerose 1y ago|0 comments
14.
by reconditerose 2y ago
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 hardware). Keep some comments out in the open lik
15.
by reconditerose 2y ago
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+ commits for a single small feature but I needed to get someone
16.
by reconditerose 2y ago
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 I cared about the community, it was more than just a p
17.
by reconditerose 2y ago
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 helped me learn a lot. I wish he had considered coming t
18.
by reconditerose 2y ago
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.
19.
by reconditerose 2y ago
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-... https://upcloud
20.
by reconditerose 2y ago
We're working on it, you can follow the progress here: https://github.com/valkey-io/valkey/issues/640 .
21.
by reconditerose 2y ago
It was always, and still is, a license issue. Redis stack had a proprietary license and now Redis has a proprietary license.
22.
by reconditerose 2y ago
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 checking, and conditionals for features like replication&#x2
23.
by reconditerose 2y ago
> 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 known as Redis didn't acquire the redis tradem
24.
by reconditerose 2y ago
The other is the company that bought the trademark https://github.com/valkey-io/valkey/issues/54 .
25.
by reconditerose 2y ago
* 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 Valkey: https:&#x2
26.
by reconditerose 2y ago
I'm from the project. There shouldn't be any caveats of replacing Redis 7.2 and early to Valkey 8.0. I've talked with a few folks who have migrated and none so far have hit any issues, one even migrated from Redis 2.6.
27.
No longer just a Redis clone; Valkey 8.0 is GA(github.com)
2 points by reconditerose 2y ago|0 comments
28.
by reconditerose 2y ago
Yeah, right now the valkey project is trying to keep full compatibility with the lass oss version of redis but improving where we can. There are plenty of concurrent hash maps attached to a tcp server that can out perform it on raw throughp
29.
by reconditerose 2y ago
Haha, we definitely used profiling tools. :) Perf is great and definitely the first tool to use. I know vtune has been used as well.
30.
Valkey achieved one million RPS 6 months after forking from Redis(valkey.io)
113 points by reconditerose 2y ago|37 comments

More ›