News for hackers. Stuff that matters.
Re:Making a Go program 70% faster by avoiding common mistakes by WillAbides on Thursday March 17, 2016 @09:47AM (#11304281)
This calculation makes sense if you compare it to miles per hour or iops. If a car went from 20mph to 30mph you would say its speed increases by 50%. Likewise, using 131ns to 76ns, this went from 7,633 per millisecond to 12,157 per millisecond which is about 72% faster.

The one that bothers me is when people say something got x percent slower.

Re:Making a Go program 70% faster by avoiding common mistakes by rileymat2 on Thursday March 17, 2016 @10:15AM (#11304441)
I guess, but I think my problem is I think of like losing money.

Sort of like losing the amount of time it takes. If I went from $100 to $50. I would say I lost 50% of my money.

Part of me feels like a 50% performance increase is another way to say that I lost 50% of the time it once took.

This is all subjective on my part.