News for hackers. Stuff that matters.
Re:Optimizing compilers reload vector constants needlessly by russianGuy83829 on Tuesday December 06, 2022 @06:59PM (#33888864)
Aren’t all speedups 3 digit percentage? As in 100% or more? Did you mean 100x?
Re:Optimizing compilers reload vector constants needlessly by why_only_15 on Tuesday December 06, 2022 @08:13PM (#33889491)
I think when people measure speedups here they deduct the first 100%, e.g. if I used to be able to process 10 items per second and can now process 20 items per second you can run 200% as fast but it's a 100% speedup.
Re:Optimizing compilers reload vector constants needlessly by janwas on Wednesday December 07, 2022 @03:09AM (#33891882)
To avoid the various ambiguities here, I learned to express speedups as a ratio of the optimized throughput, divided by the baseline throughput. Or equivalently: the baseline time divided by optimized time.

4400 MB/s vs 800 MB/s = 5.5x speedup or 5.5 times as fast.

Re:Optimizing compilers reload vector constants needlessly by tim-- on Tuesday December 06, 2022 @07:12PM (#33888980)
A three digit percentage means at least a quarter of the time, but possibly more.

Something that is 50% faster will take half the time. Something that is 100% faster will take a quarter, and so on.

Re:Optimizing compilers reload vector constants needlessly by anonymoushn on Tuesday December 06, 2022 @08:30PM (#33889621)
Something that is 50% faster takes 2/3 as long sir.
Re:Optimizing compilers reload vector constants needlessly by hvs on Tuesday December 06, 2022 @10:40PM (#33890390)
You are correct, but I would also point out that I have to think long and hard about this whenever it comes up.