Hacker News new | ask | show | jobs
by Nomentatus 3186 days ago
Yes, I often have done such refactoring. It's hard to get that last 20% of speed, much less last 5% without making a large number of small changes in code, usually after getting accumulated trace results (however presented.) .1% = one in one thousand. Keep stacking up those improvements and you do get somewhere, and often you'll easily find one hundred very small improvements in a day (10% altogether!) if it's green code, along with the bigger inefficiencies to fix. Not to mention that ignoring a presently-small inefficiency is predicting that future use won't swell that into a problem - which can be most unwise. Also, looking for tiny improvements gives you a good chance to stumble upon larger improvements you'd missed earlier. Optimize much?
1 comments

You’re doing a lot of hand waving: “One hundred small improvements in a day” That’s a lot of work in an 8-10 hour day...

“if it's green code,..”

My point is that you don’t start by looking for 0.09% improvements when you’re profiling your code.

As for climate change, we are looking for cleaner energy options. The world’s energy use is going to increase greatly as billions more come out of poverty. China, for example, is going to increase nuclear energy to be almost on par with the US over the next decade:

https://www.nextbigfuture.com/2017/09/china-will-more-than-d...

Ya made me look - but no, you weren't saying starting. Nothing of the kind.