4 ms·
More likely for people on that path, there's bigger wins from paying down technical debt that exists at a higher level than by trying to optimize your code's me
by thwarted 15y ago
More likely for people on that path, there's bigger wins from paying down technical debt that exists at a higher level than by trying to optimize your code's memory access patterns.
- sliverstorm 15y agoThat depends. Money spent on hardware buys you linear performance improvements. Algorithmic improvements can buy you exponential performance improvements. There is most certainly a point where money spent on hardware gives a better return, but all the hardware in the world couldn't net you acceptable runtimes using bubblesort on colossal datasets.
- cube13 15y agoI agree completely. Frontend optimizations can probably give a lot more in the short term than these kinds of backend optimizations. Unfortunately, even if it's paying down technical debt, if you're trying to squeeze out more cycles with your low-level code, a lot of the time it's issues on the algorithm level. When refactoring there, these kinds of optimizations should always be at the back of your head, even if it's just to explain why moving the for loop up 5 lines gave the function a 2% performance boost.