31–40 of 225 posts
I'm also curious about those slow 1990s SSDs.
The slider is very bad UX : I missed it too at first. It is not pronounced enough, partly because it is all the way to the right. A former boss would say : make it red .
I sympathise that the site probably wasn’t designed with mobile in mind, but it’s impossible to go beyond 2015 without hitting the GitHub link.
Not an intuitive thing but the data is fascinating. A couple of notes of people who are confused by it: 1) The 'ns' next to the box is a graph legend not a data label (normally that would be in a box labeled legend to distinguish it from graph data) 2) The weird box and rectangle thing on the top is a slider, I didn't notice that until I was looking at the code and said "what slider?" 3) The only changes from 2005 to…
"And that means Amdahl's Law is more important than Moore's Law these days." idk, sure seems like we could have 1-2 cores (permanently pegged?) at 5 ghz for UI/UX then ($money / $costPerCores) number of cores for showing off/"performance" by now. But the OEMs haven't gone that way.
I'm more familiar with the 2001-2006 era where redis-like RAM caches for really hot data made a lot of sense, but with spinning rust a disk drives, it made more sense to go over the network to a microservice that was effectively a big sharded RAM cache than to go to disk.
Seems like you could push more hot data to the very edge these days and utilize SSDs like a very large RAM cache (and how does that interact with containers)?
I guess the cost there might still be prohibitive if you have a lot of edge servers and consolidation would still be a big price win even if you take the latency hit across the network.
Amazing performance improvements, except no improvement at all on the packet roundtrip time to Netherlands. Someone should really work on that.
How are people practically taking advantage of the increase in speed of SSDs these days compared to network latencies? It looks like disk caches directly at the edge with hot data would be the fastest way of doing things. I'm more familiar with the 2001-2006 era where redis-like RAM caches for really hot data made a lot of sense, but with spinning rust a disk drives, it made more sense to go over the network to a mic…
Presumably video editing or something might get more of a win but I don’t know.
An instructive thing here is that a lot of stuff has not improved since ~2004 or so, and working around those things that have not improved (memory latency from ram all the way down to l1 cache really) requires fine control of memory layout and minimizing cache pollution, which is difficult to do with all of our popular garbage collected languages, even harder with languages that don't offer memory layout controls, a…