man I love this.. so when i did regular signale threaded optimization i got my algo from 16.7 minutes down to about 1 minute Now I moved to multithreading and it runs in about 5 seconds.
Never skip your optimizations people!
@freemo Optimisation must, however, be done at the correct time.
And the correct time for optimisation is (usually) *after* you've done everything else you need to do with that program; because a lot of optimisations make it very tricky to *change* things later.
@freemo Oh, it’s definitely something to take on a case-by-case basis. Optimisation is something you want to do before putting your project into actual production; and yes, you do want to ensure that your program passes all the tests after optimisation.
And yes, in some cases, the program might not even run unoptimised. Then you might need to optimise early, just in order to get anything done at all.
“Optimise late” is not, in any way, intended as a hard and fast rule. Rather, it’s suggested as a useful bias - in many but not all situations. And if you can identify whether or not it’s a good idea in any particular situation… then you already know enough to know when to ignore that suggested bias.