Great news! BTW, could you please point out test WU that best suitable for speed comparision?Sure whole bunch gives most precise picture but maybe some faster approach is valuable for comparision of different systems?
According my own tests SSSE3 64bit under 64-bit OS is the best one for such CPUSo right now probably KWSN_2.4V_SSSE3_MB.exe is the leader (from 2.4V_Windows_x64_SSSE3 archive)
Ok Hope they post some info about testbench used here. Wonna get comparable results on my systems too Some database with test times on different app builds/OSes/ CPUs will be useful IMHO
I use 1.43 knabench too, will run with your WUs now Thank you!P.S. this test loads only 1 core. As I see from your test file you run it on quad. Did you manage all cores loading with app binding to core (some CPU affinity) ?imagecfg.exe from test bench doesnt work for me (is it only for NT4 ?)...
Yes, this testbench uses only 1 core. My question is : is any test-bench exist to correctly test full-cores-load run times?AFAIK conroe has common L2 cache for cores so real situation for app when it runs in parrallel on all available cores quite different from single core run.It's interesting to compare full-load run-times on Core2 Duo/Quadro with Athlon 64 X2 version IMHO.
I know, i fixed that one 2 hours ago.
...is any test-bench exist to correctly test full-cores-load run times?
Quote from: Raistmer on 03 Sep 2007, 05:43:08 pm...is any test-bench exist to correctly test full-cores-load run times?When running more than one application instance, there is contention for resources. To test all the possible scenarios of different WU angle ranges, offsets of start time, etc. simply would have too many variable effects to permit repeatable tests. That's why the test program shuts down the BOINC service if it's running and does everything on one core.I don't say a multiple test is impossible, but the amount of time spent testing many scenarios would be more than we can expect volunteer testers to contribute. Joe