23,328 RulesMaxxus@sh.itjust.works to 196@lemmy.blahaj.zone – 690 points – 8 months ago33Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentI always knew tomatoes were unoptimizedSomeone compiled tomatoes without -O3Go with -Os to optimise for codesizeOften faster anyways as the CPU is eating through instructions faster than the RAM can keep up with. May or may not require compiling as x86-64-v2, depending on code. In general, never trust performance you didn't benchmark.
I always knew tomatoes were unoptimizedSomeone compiled tomatoes without -O3Go with -Os to optimise for codesizeOften faster anyways as the CPU is eating through instructions faster than the RAM can keep up with. May or may not require compiling as x86-64-v2, depending on code. In general, never trust performance you didn't benchmark.
Someone compiled tomatoes without -O3Go with -Os to optimise for codesizeOften faster anyways as the CPU is eating through instructions faster than the RAM can keep up with. May or may not require compiling as x86-64-v2, depending on code. In general, never trust performance you didn't benchmark.
Go with -Os to optimise for codesizeOften faster anyways as the CPU is eating through instructions faster than the RAM can keep up with. May or may not require compiling as x86-64-v2, depending on code. In general, never trust performance you didn't benchmark.
Often faster anyways as the CPU is eating through instructions faster than the RAM can keep up with. May or may not require compiling as x86-64-v2, depending on code. In general, never trust performance you didn't benchmark.
I always knew tomatoes were unoptimized
Someone compiled tomatoes without -O3
Go with -Os to optimise for codesize
Often faster anyways as the CPU is eating through instructions faster than the RAM can keep up with. May or may not require compiling as
x86-64-v2, depending on code. In general, never trust performance you didn't benchmark.