4 ms·
I'm not convinced there's much (non-real-time) software where performance places legitimate constraints on deadlines. I've seen exactly one case before, which
by johnday 7y ago
I'm not convinced there's much (non-real-time) software where performance places legitimate constraints on deadlines.
I've seen exactly one case before, which was an ancient script running on a mainframe in a bank which took 6 hours to complete overnight. [And, by the way, correctness is still more important in this case!]
But 99.999% of the time, your code's performance is not the final word.
- falcolas 7y agoHere's one: "1 second of loading lag time would cost Amazon $1.6 billion in sales per year." ~Amazon Here's another: "An extra 0.5 seconds in each search page generation would cause traffic to drop by 20%" ~Google
- jdbernard 7y agoBoth of those pre-suppose that the software already exists and is already doing things correctly. Non-functioning software would cost Amazon all of it's sales per year.
- falcolas 7y agoWhy make the assumption that performant software and functional software are somehow on the opposite side of the spectrum of what's possible? The point of the article is that performance is just as important to consider in addition to functionality and correctness. To use an analogy, it's easier to make a house energy efficient if its considered from the beginning, than if it's tacked on afterwards. In fact, tacking it on afterwards is sometime impossible without a complete renovation (analogous to re-writing the software).