If you frequent the IRC channel, you'd know me and avansc have been having a kindof dual with eachother. Our weapons are equation solvers which we wrote ourselves. Avansc created cQuate and I made eQuasian. As you can probably tell avansc gave my solver its name(I was going to go with AsianKid but whatever). Anyway Round 1 finished and I got my ass kicked.
Here are the results for cQuate(mk2) VS eQuasian(mk1).
so qp ran both our code, and I fell behind again. But I know why when I cleaned up my source after. Unused functions and stuctures impacted on my speed, when I removed em I got a good 2s speed boost. So I'm gonna have qp take em out and re-profile, if my code beats avanc's it's 1 to me. But as it stands right now it's cQuate(MK2): 2 eQuasian(MK2): 0
Cumulative Average per batch of 4 random equations of equal length.
All times in milliseconds (mSec) unless otherwise noted.
Test Machine: AMD PhenomII 920 x4, 4GB PC28500, Windows7 x64 Professional
Metered With: Microsoft Visual Studio Team System instrumented system profiler.
All tests are performed w/ release builds and *CODE OPTIMIZATION OFF!* to avoid sneak compiler optimizations.
Consistency verified by sampled profiler.
BATCH COUNT EXECUTION TIME
Avansc M_D_K
Small Equation
---------
1000----> 4.2233 mSec 6.283333 mSec
10000---> 566.8325 mSec 583.04 mSec
500000--> 29500.98 mSec 34326.19 mSec
Large Equation
---------
1000----> 17 mSec 30.9166 mSec
10000---> 2012.0233 mSec 2261.3433 mSec
500000--> 100232.48 mSec 113104.02 mSec
Btw the junk code in question was an indexer I wrote but never bothered to test or use since it wouldn't have worked with how I handle the equations.
Gyro Sheen wrote:you pour their inventory onto my life
IRC wrote:
<sparda> The routine had a stack overflow, sorry.
<sparda> Apparently the stack was full of shit.