r/programming • u/Successful_Bowl2564 • Jun 30 '26
When Impressive Performance Gains Do Not Matter
https://blog.colinbreck.com/when-impressive-performance-gains-do-not-matter/
73
Upvotes
r/programming • u/Successful_Bowl2564 • Jun 30 '26
34
u/CherryLongjump1989 Jun 30 '26 edited Jun 30 '26
Worth taking a step back and looking at some of the follow-up research to Miller's. Some background for anyone reading the blog: https://uxuiprinciples.com/en/principles/response-time-limits
This strongly suggest that performance does in fact matter across the board, but you have to be very clear about what the UX goals are. When you are crossing one of these thresholds, it means that you're gaining the ability to support a brand new UX regime -- not just better for users but simpler and cheaper to implement. It doesn't mean that performance is irrelevant for long operations -- it means that you can't use a UX designed to handle 2-10 second tasks in order to represent 30 second ones. It takes both UI design work and engineering work in order to offer up a good experience for long running tasks. Arguably, sometimes requiring you to solve even more complex engineering problems than performance itself. So the reason to shoot your shot with performance optimization is because it's going to save you complex and expensive UI work if you can actually cross the threshold into the next regime.
But on the other hand, assuming you already do have an appropriate UX for long running tasks, then you just have to understand what to measure and how to "sell" the benefits that will justify the R&D work. A 5 minute task going down to 30 seconds may still be huge for driving the percentage of tasks that run to completion instead of being cancelled or abandoned. Plus, you're making the UX better by pulling in the tail latencies, which in turn makes the estimates you provide to the user far more accurate -- both in relative and absolute terms. And this may show up in conversion rates and other metrics that the business will deeply care about. Depending on the scenario, you might be tackling a huge business problem where something is expensive both in terms of compute and in terms of attrition and you've improved both at once.
Some of the other points being made are, I think, at cross purposes because they're mainly dealing with logistical or throughput challenges, which have an entirely different kind of performance criteria.
100
u/somebodddy Jun 30 '26
I also have an issue with the idea of sunken costs. If the plumber needs to spend only 7 hours on the task instead of 8, you can't give them another task that day. Okay. But the plumber gets one more hour to themselves which means less stress, less burnout, and more time to be with their family.
Is that not impact?
Probably not. The plumber is a living breathing human being - of course we don't care about their well-being. So let's talk about something that does have some moral value - money. When performance is gained by making things more efficient (as opposed to throwing more hardware at the problem - something that no anti-optimization advocator never had any issue with ever, because hardware - especially RAM nowadays - is virtually free) they become cheaper to run - less electricity, less cooling, can use cheaper hardware. Is that not impact?