4 ms·
Sure: https://github.com/iamdanfox/QwirkleSolver https://github.com/iamdanfox/QwirkleSolver The Rust version has had some algorithm improvements to reach 0.015
by iamdanfox 12y ago
Sure: https://github.com/iamdanfox/QwirkleSolver https://github.com/iamdanfox/QwirkleSolver
The Rust version has had some algorithm improvements to reach 0.015s, but it was conceptually identical when it was solving in 0.7s.
- thom 12y agoObviously this is mostly for kicks, but there's a lesson in the 45x speedup improving the algorithm vs the 4x improvement changing technologies. :)
- mike_hearn 12y agoTaking a quick look, it seems the program starts up, runs once and then quits. I'm wondering if the JIT actually compiled all of the app. Being JVM based Scala is very profile guided, so normally for benchmarks you want to repeat the same operation in a loop until elapsed time stabilises. That said, if your use case involves running once for a few seconds and then quitting, ahead of time compilers like rustc will always beat a profile guided JITC. So this may be an unfair point.