4 ms·
Not if “faster” refers to computation rate rather than runtime, in which case it becomes 100/81 i.e. 23% faster.
by ummonk 3y ago
Not if “faster” refers to computation rate rather than runtime, in which case it becomes 100/81 i.e. 23% faster.
- moomin 3y agoYes, but I’ve literally never heard anyone say that.
- kaashif 3y agoIt's not really possible to tell if someone saying "50% faster" means a 50% speed increase or a 50% time decrease. Even in other contexts it can be ambiguous. Yesterday I drove 60mph, today I drove 50% faster. Yesterday I got there in 1 hour, today I got there 50% faster. It's not really possible to tell them apart without looking at the numbers.
- ummonk 3y agoYou've never seen anyone say "x% faster" where x is a number larger than 100? I find that hard to believe.
- squeaky-clean 3y agoNot for a programming language because it's extremely rare for the computation rate to increase, rather than the work being done to compute something decrease. If you've rewritten something to better use cachelines, removed saturating memory bandwidth, etc then sure you've increased The computation rate. But that's rarely how these language specific optimizations occur.
- chalst 3y agoI have, in technical descriptions of compilers.