News for hackers. Stuff that matters.
Re:Making a Go program 70% faster with a one character change by enedil on Monday November 14, 2022 @02:46PM (#33599849)
I do not agree. When you benchmark you usually measure the differences between times needed to complete. This is because it is highly non-obvious that if you increase workload twice, the time increases also twice. Perhaps the algorithm is not linear. Perhaps if you have more data, you suddenly need to swap memory. Perhaps something (like disk access in parallel) means that actually it takes less than 2x time. This means that a concept of speed per unit of work is undefined. So the only reasonable interpretation of "70% faster" means "spends 30% time of original".
Re:Making a Go program 70% faster with a one character change by yongjik on Monday November 14, 2022 @04:09PM (#33601104)
But under your definition, if something becomes "three times as fast" (i.e., 200% faster), it will have to finish its task in negative time!
Re:Making a Go program 70% faster with a one character change by wizofaus on Monday November 14, 2022 @04:12PM (#33601157)
I can categorically state I've never thought of or understand 70% faster as meaning that, and certainly not 100% faster as meaning "completes instantly".

I see the OP has solved the problem by removing any references to how much faster from the article title!