romange

6 ms·

1.
by romange 2y ago
Valkey/Redis support offloading of io processing to special I/O threads. Their goal is to unload the "main" thread from performing i/o related tasks like socket reading and parsing, so it could only spend its precio
2.
by romange 2y ago
Dragonfly supports both epoll and iouring, and polling engine choice is quite orthogonal to its shared nothing architecture. I do not think that Valkey or Redis will become fully multi-threaded any time soon - as such change will require bu
3.
by romange 3y ago
I apologize. I must say that my tone, as you rightly wrote, was inappropriate. Indeed, I am the lead developer for Dragonfly. As such, I am deeply concerned with the performance aspects of our product. Dragonfly claims to be a drop-in, bett
4.
by romange 3y ago
I understand what you are saying. How would you suggest to present it then? Dragonfly is not faster than Redis when running on a single cpu. It can not be, just because it has the overhead of the internal virtualization layer that composes
5.
by romange 3y ago
Absolutely. And I am sorry I reacted this way.
6.
by romange 3y ago
1. We removed the FAQ page 2. You are right, I need to shut the fuck up and let self-righteous hn crowd with torches do what they do best - find a weakness, and push it until they get bored and switch to beat another builder. You asked me a
7.
by romange 3y ago
I personally benchmarked Dragonfly vs Memcached. Are you calling me a liar? :) Do you think I also photoshopped this document? https://github.com/dragonflydb/dragonfly/blob/master/docs/me...
8.
by romange 3y ago
You are an exception, then :) But I still stand by the claim that fragmenting your stateful workload (i.e. Redis) into bunch of processes instead of having a single endpoint per instance is an acceptable approach in 2023. When your processe
9.
by romange 3y ago
This is definition of spam: https://www.merriam-webster.com/dictionary/spam To the best of my knowledge this page was not sent to anyone.
10.
by romange 3y ago
Because we focus on building the most awesome datastore and you should decide whether you prefer having your store designed by good marketeers or good engineers.
11.
by romange 3y ago
hmm and ships are designed to sail, yet you use planes to cross atlantic. Nokia was designed as strongest and most affordable phone, yet you use Iphone that costs 1000$. it's not about how it was designed but whether it addresses your
12.
by romange 3y ago
We do not fight off capitalism in any way. Rather, I view capitalism as a powerful engine driving innovation. My experience as an engineer at both Google, a massively profitable entity that contributes significantly to the open source commu
13.
by romange 3y ago
We are reading this and we will fix it shortly.
14.
by romange 3y ago
You are absolutely right, and I apologize for having this experience. SEO is part of the game, but it should not be in FAQ section.
15.
by romange 3y ago
I think using word "misleading" is also "misleading". Dragonfly hides complexity. Docker hid complexity of managing cgroups and deploying applications. S3 hid complexity of writing into separate disks. But you do not ca
16.
by romange 3y ago
KeyDB implements multiple threading with spin-locks that protect a global shared data structure. Dragonfly is built upon shared-nothing architecture where each thread manages its own slice of data, hence no need for classical locks and no c
17.
by romange 3y ago
It compares a process with a listening port with another process with a listening port. To give another example - nobody compares minio with bunch of disks to which you can write separately, and probably more efficiently.
18.
by romange 3y ago
Not yet but it supports JSON API
19.
by romange 3y ago
It does not have to be instead of our startup, really.
20.
by romange 3y ago
I made an honest mistake. While I saw DragonflyBSD, I didn't realize its prominence within the BSD community. I assumed that since our project only focuses on Linux, having a similar name in a different "namespace" wasn'
21.
by romange 3y ago
DragonflyDB cofounder here. I am not shy about our choice of license. Like with software design, everything is about trade-offs. Folks here voiced reasons why we chose BSL. I am sure you perfectly aware about all this. I do not know person
22.
by romange 3y ago
Dragonfly is better with 1. Memory utilization (read the announcement, they mention it) 2. Deployment/orchestration - your initial threshold that forces you to scale horizontally just went up by order of magnitude. In fact for many us
23.
by romange 3y ago
BSL license is more company-friendly than AGPL.
24.
by romange 3y ago
Yes, you can - in fact it supports out of the box existing frameworks and clients like redisson, sidekiq and many others
25.
by romange 4y ago
here is the twitter thread :) https://twitter.com/romanger/status/1596794193849987072
26.
by romange 4y ago
I did not claim that DrashCache is "the absolutely best" algorithm. But some caching algorithms could be better than others on real-world data. Would you want me to run something like https://github.com/twitter&#x
27.
by romange 4y ago
Backward compatibility is good? I disagree with you regarding this specific case. Redis philosophy is to add more and more settings, requiring from an end-user to understand internals and low-level trade-offs. And I am sorry, but in the cas
28.
by romange 4y ago
I agree. This is why DashCache is designed to be very efficient in terms of CPU and memory, while providing very strong adaptive capabilities for mixed workloads. If think the most important part in this design is the realization that we do
29.
by romange 4y ago
If Redis LFU mode improved LRU then why they kept the LRU mode? The official recommendation by Redis is to use LRU. https://redis.io/docs/manual/eviction/
30.
by romange 4y ago
Hi, I am the author of Dragonfly. Following this post, I performed the loadtest on instance m5.4xlarge, recorded myself and posted the video here: http://assets.dragonflydb.io/videos/video2609676488.mp4 the command I u

More ›