jdsully

29 ms·

301.
by jdsully 5y ago
The argument for Calibri was documents were being consumed more on the screen than on paper. Serif’d fonts were considered more legible on paper but not on low res screens of the day. An argument could be made that with high res screens now
302.
by jdsully 5y ago
KeyDB uses a custom lock I wrote called the “fastlock”. At its core it’s a ticket lock with some tweaks to better tune it to KeyDB. When uncontested it’s a single atomic increment. When contested ownership changes extremely fast. If we spin
303.
by jdsully 5y ago
KeyDB is a few % slower single threaded right now, but we have some cool announcements coming in that regard. Some people use us for Active Rep or some of our other custom commands rather than just the Multithreading.
304.
by jdsully 5y ago
Elasticache is already that competitor. They are scary to be sure but they have some weaknesses. The main one is branding: Elasticache is a white label Redis not it’s own thing, to the point where their own docs use the two interchangeably.
305.
by jdsully 5y ago
Take the scenario where you have an 9 node redis cluster. With KeyDB you could shrink that down to 3 nodes with 3 threads while getting the same throughput. This reduces the maintenance burden while also reducing latency. There's ove
306.
by jdsully 5y ago
We have our FLASH feature which gives us a baseline persistence story, you don't need RDBs or AOFs anymore. However there's a lot of work left to do in this area. The long term goal of KeyDB is to let you balance your dataset acr
307.
by jdsully 5y ago
They have Elasticache which is always a concern. In terms of open source projects my read is they really don’t want to run their own and are much more comfortable operating open source as a service. They “forked” Elastic Search 2 years ago
308.
by jdsully 5y ago
Yea that was roughly KeyDB’s original design. There’s some nuance in the locking like ensuring it’s both fair and fast so P99 latency doesn’t get out of control. In the Enterprise codebase we can take snapshots which lets us do reads withou
309.
by jdsully 5y ago
I’ve learned to appreciate Salvatore’s stance on simplicity the longer we’ve gone on with KeyDB. But when I first made KeyDB two years ago I was really perplexed at the decisions he made with respect to threading. It’s not my intention to b
310.
by jdsully 5y ago
There are a few, some predate us like Threadis. Most only offer a subset of the Redis feature set where we really wanted to be a drop in replacement.
311.
by jdsully 5y ago
The FLASH feature in Enterprise can send all writes to disk before replying +OK, however notably we don’t fsync (AOF is still recommended if you need that). In these deployments it’s not necessary to use RDB or AOF except for replication. A
312.
by jdsully 5y ago
Long running commands are still a problem. We have infrastructure in the Enterprise version to alleviate this but so far we’ve enabled it only for KEYS and SCAN. MGET does come up frequently so it’s on our radar.
313.
by jdsully 5y ago
They’re users. We were pretty bad at asking for logos and just started down that road. Honestly if I had one regret it’s not doing more user outreach.
314.
by jdsully 5y ago
Yea FLASH is only in the Enterprise version. At a rough level the open source is the best cache we can make while pro/enterprise is the best full featured database. It’s not fully there yet but the end goal is you can get caching and
315.
by jdsully 5y ago
Their biggest crime seems to be they just aren't great developers. If you look at the patches they presented which to their knowledge were correct you'd see they couldn't have done anything useful. Because of their earlier
316.
by jdsully 5y ago
It would be nice to have transparency on mod actions like we have with user actions (aka showdead). People are rightfully more nervous as other platforms are switching to heavy handed moderation.
317.
by jdsully 5y ago
That’s more reasonable in my opinion.
318.
by jdsully 5y ago
Your senator makes decisions based on public will and letter writing is a proxy for that. They have a team to deal with the inflow. Your average PhD student isn't equipped in the same way to deal with an outraged public.
319.
by jdsully 5y ago
I guess the question is what more is there to accomplish? They’ve been banned and I gurantee they already know the community is pissed. Is filling up their inbox with angry emails going to actually help in any way?
320.
by jdsully 5y ago
Unless you are an involved party you're just adding to the mob. The kernel maintainers said their piece there's no need for everyone to pile on.
321.
by jdsully 5y ago
In the old days they used to print giant books of these "phone numbers" and drop them on your neighbours porches. Odd how things that were common are now security risks.
322.
by jdsully 5y ago
Ignorance was a theme of many past bubbles. In the 20's it was the common man not understanding stocks. In the 80s it was "Savings and Loans are just banks, they're safe!". '08 it was "They wouldn't giv
323.
by jdsully 5y ago
Canada's M1 is up 27%, M2 up 20% over the last 12 months. They aren't printing nearly as much as the US but it's still dramatic vs prior years.
324.
by jdsully 5y ago
There is a “flamewar” filter that derates content with too many back and forth replies.
325.
by jdsully 5y ago
The problem is rarely with the courts most people don't lose lawsuits like that. The problem is when the real person goes to the bank for credit and can't get it because the bank thinks you are already in default.
326.
by jdsully 5y ago
Intel still has 60% market share so the majority are still buying Intel, but the trend is very clear. Expect more AMD options to come out in the coming months.
327.
by jdsully 5y ago
I have an 8GB M1 air. It's fine on day one when you power it on and have a single safari tab, but leave a few things open and its swap hell. The SSD may be fast but it really takes away from the magic when your waiting multiple secon
328.
by jdsully 5y ago
They did a ton of design work during the original Opteron days when it was performance king, only to have it be wasted as AMD flubbed the next gen and circled the drain for 10 years. Vendors are noticeably cautious this time around, but the
329.
by jdsully 6y ago
NVIDIA called it their first “data center CPU”. Our helpful reporter simplified it to the point of being flat out wrong. Not uncommon.
330.
by jdsully 6y ago
The windows org flat out refused to implement combined engineering, so upper management forced the issue by laying the testers off. In the Office org management did what they were supposed to and it was as you described.

More ›