Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
reconditerose
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
reconditerose
2y ago
The biggest per core "efficiency" improvement will come from RDMA, since IO tends to be the largest bottleneck in Redis (and now Valkey). However, if you are running with deep pipelines (sending multiple commands as a batch withou
32.
▲
by
reconditerose
2y ago
This is basically the original source of the claim, https://valkey.io/blog/unlock-one-million-rps/ . We are working on a followup that goes more into depth about how to setup the benchmark so that is easier to repr
33.
▲
by
reconditerose
2y ago
FWIW, Redis was previously mostly developed by the community but the trademark was acquired by a VC funded tech company. AWS, and other cloud providers like Tencent, were contributing to Redis and they went ahead and changed the license any
34.
▲
Valkey 8.0.0-Rc1 is out, focusing in performance and reliability
(github.com)
4 points
by
reconditerose
2y ago
|
1 comments
35.
▲
by
reconditerose
2y ago
Valkey (an open-source alternative to Redis) has it's first release candidate for 8.0. A sample of some of the features: * A new I/O threading architecture that allows dynamically adding and removing threads and increasing the max
36.
▲
by
reconditerose
2y ago
I haven't looked at the topic since we created the fork, and I'm surprised people weren't still arguing about it. There were a lot of vary passionate people in the beginning, but very few of them actually contributed and most
37.
▲
by
reconditerose
3y ago
> I'm not sure that this is true, at least not the commercial part. Redis clients are pretty simple (compared to Redis itself, at least). I'll get on my soap box then. The redis client ecosystem is fractured and awful, and it&#
38.
▲
by
reconditerose
3y ago
As someone who has extensively worked on a Redis fork at AWS and worked with the company for 6 years, I wouldn't worry about Redis merging stuff from Valkey. We believe they refused a huge number of PRs because we believe it would have
39.
▲
by
reconditerose
3y ago
Hey, I am one of the maintainers of Valkey, I'll try to answer. I think there is a few things I would like to see in the mid to short term. We're trying to make a lot of the core datastructures more efficient (both in terms of mem
40.
▲
by
reconditerose
3y ago
Hi, co-creator of Valkey here. I'm not that worried about it. There are a lot of people who have tried to maintain Redis folks, my employer AWS has one such fork I know very well, and they quickly become extremely hard to maintain with
41.
▲
by
reconditerose
3y ago
> I also disagree with that post’s assertion that Redis contributions would have been withheld if it started with a different license. I expect contributions would come from existing users of Redis who wanted new features themselves and
42.
▲
by
reconditerose
3y ago
Drew seems like a great guy, but he wasn't the one maintaining Redis when the relicense happened. There are non-Redis contributors who are trying to figure out what to do nest, and people keep peppering me (one of those contributors) a
43.
▲
by
reconditerose
3y ago
> I don’t think I’m happy with the licence choice here (it should stay BSD-3-Clause). At least the primary repository isn’t on sourcehut, people might actually contribute to it. The old development community is regrouping under https:&#
44.
▲
by
reconditerose
3y ago
Several Redis maintainers and contributors moved to development here, https://github.com/madolson/placeholderkv . KeyDB is not bad though, it's an older fork that isn't very widely adopted.
45.
▲
by
reconditerose
3y ago
> They get paid for it. Don't try to spin this as if it's someone people working on it in their spare time out of the goodness of their heart. It's just their job. No, you can't have this both ways. I'm the main
46.
▲
by
reconditerose
3y ago
The beef I have here is that Redis also takes credit for community work. Most of the heavy lifting came from antirez, who created and ran the project up until 2020. (It's worth conceding that Redis did compensate antirez). At that time
47.
▲
by
reconditerose
3y ago
Don't worry, if there is a fork that is the first thing I will contribute to. I build one that prints out various fractals, but never contributed it.
48.
▲
by
reconditerose
3y ago
Exactly. Redis (the company) had plenty of opportunity to monetize either a cloud offering or their enterprise offering. They have a lot of cool technology like vector search and time series extensions that people will readily pay for. They
49.
▲
by
reconditerose
3y ago
Redis was open before the trademark was acquired from antirez by Garantia Data, who then re-branded themselves as RedisLabs, and then as Redis. This was definitely not a predestined outcome, there are plenty of other foundational open sourc
50.
▲
by
reconditerose
3y ago
Yeah, https://redis.com/press/redis-ceo-succession/ , seems to be the case here. It took them a little over a year to decide open-source isn't profitable and move away.
51.
▲
by
reconditerose
3y ago
Redis Inc. is moving the https://github.com/redis/redis/ project away from the three part BSD license to a dual license using two non-OSI approved license. This comes after previous comment from them saying that &
52.
▲
by
reconditerose
3y ago
For those that don't click through, the announcements is more of a preview, and has limited scope (only supports a subset of the commands and only support Python and Node). It's entirely open-source with a liberal license and you
53.
▲
by
reconditerose
3y ago
This has nothing to do with licensing. The motivation was that the various Redis clients are inconsistently being maintained, have different features, and perform differently. Having a core rust implementation handle the heavy lifting makes
54.
▲
by
reconditerose
3y ago
It's really bad. The problem is that the swapping of pages is constantly stalling the main Redis thread, which is not built for parallelism. Redis is built around a single highly efficient thread, so stalling it for 250us to pull a pag
55.
▲
by
reconditerose
3y ago
I'll bite. I think with most relational and document databases, my view of the "classical world", you are often storing all of your data in tables or documents in a structured way. Normalizing the data where possible. You
56.
▲
by
reconditerose
3y ago
It is part of the drive to make Redis "more like your classic database," he said. In the future, support for natural language queries and enhanced vector and feature store capabilities will be added. Seems way off the mark for w
57.
▲
OSS Redis 7.2 is now GA
(github.com)
1 points
by
reconditerose
3y ago
|
1 comments
58.
▲
by
reconditerose
3y ago
Release is focused on incremental performance and memory improvements to various datastructures, a couple of new commands, and minor features to improve manageability.
59.
▲
by
reconditerose
4y ago
I wouldn't take their latency numbers too seriously since their measure isn't relative to the throughput. It's not always obvious, but the latency of high performance is tightly coupled with throughput. The latency of high pe
60.
▲
by
reconditerose
4y ago
It's just marketing.
More ›