3 ms·
No optimization is worth the effort before profiling. If they found out that these operations are responsible for long enough delays, or high enough energy con
by nine_k 6y ago
No optimization is worth the effort before profiling.
If they found out that these operations are responsible for long enough delays, or high enough energy consumption spikes, it would make all the sense to optimize them.
- jonstewart 6y agoProfiling is good at telling you which parts of your code account for most of the program’s runtime, but that’s it. It can’t tell you whether the performance is reasonable relative to the work done, or whether a totally different approach is necessary. Writing fast code goes well beyond using profilers, in keeping with the article’s thesis.
- nine_k 6y agoAssume you locate a part of code which is 10x as slow as it could be. You make it 10x faster; great! But that part only took 1% of the total perceived processing delay, so the user sees a whooping 0.9% improvement.
- vnorilo 6y agoHowever, you need to have a big picture view or potential optimizations when you architect. The profiler can't save you from slow architecture.