A10-5745M results.

[QUOTE=tului;386305]A10-5745M results.[/QUOTE]
Thank you for that one too. Your A10 will most likely benefit from using VectorSize=4. Would you mind changing that in the .ini files and just rerun the m-gs-<nn>-<nn> tests (skip the long-running *fulltest.ini and *GCN*ini tests)? And please add an m-gs-128-32.ini file. Copy from m-gs-128-16.ini and set GPUSieveProcessSize=32. Then, please run mfakto [-d ..] -i m-gs-128-32.ini --perftest > m-gs-128-32.log

Now, that I have the "automatic" evaluation of kernel speeds, I will think about auto-adjusting VectorSize as well, but we're not there yet.

[QUOTE=Bdot;386275]Very nice! All seems to work as expected. I'll need a bit more time to go through the results, the first things I noticed:
[LIST][*]290x seems to have major improvements in int32 performance: the 32-bit kernels are now 20% faster than the 15-bit ones (on previous GCN, they are 15% slower). As the current code does not yet honor this, expect a 20% performance boost with the next mfakto version, and no more performance drop at the 73-bit-boundary.[*]290x behaves pretty much like GCN regarding ini file settings: according to these tests, GPUSieveSize=126 and GPUSieveProcessSize=24 should be fastest on this card as well.[*]290x: Measuring the CPU-sieve-based TF kernels only worked for the smallest exponent, the other results are way too low - either something overflowed, some throttling kicked in or my test did not fully utilize the GPU.[*]1/8 DP rate on 290x is not sufficient to give DP calculations an advantage over SP. Therefore, only Tahiti and Malta chips will use DP in mfakto. Has anyone still some HD5870/5850 sitting around? This one would also be a good candidate.[*]HD4600 worked well, delivering 18-19 GHz-days/day for current LL test range.[*]performance dependency to the exponent size is stronger than I expected, e.g. 290x: 975GHz (2M), 770GHz (39M), 739GHz (78M), 684GHz (332M), 616GHz (4200M).[*]I missed to include an m-gs-128-32.ini file. Could you please copy from m-gs-128-16.ini and set GPUSieveProcessSize=32. Then, please run mfakto [-d ..] -i m-gs-128-32.ini --perftest > m-gs-128-32.log
I think I know the outcome for HD7770, but HD4600 and R290x would be interesting.[/LIST][/QUOTE]

[ATTACH]11893[/ATTACH] edit: hmm, and an extra 0.5 ghz-day/day if numstreams=5 vs 3...

[QUOTE=Bdot;386275][LIST][*]I missed to include an m-gs-128-32.ini file. Could you please copy from m-gs-128-16.ini and set GPUSieveProcessSize=32. Then, please run mfakto [-d ..] -i m-gs-128-32.ini --perftest > m-gs-128-32.log
I think I know the outcome for HD7770, but HD4600 and R290x would be interesting.[/LIST][/QUOTE]

Late result, sorry...
Intel HD4600

[ATTACH]11917[/ATTACH]

[QUOTE=AK76;386588][ATTACH]11917[/ATTACH][/QUOTE]

Something's quite wrong there... the results are quite different from NickOfTime's 290X results, the 290 should be not much slower than it's X version..

[QUOTE=kracker;386593]Something's quite wrong there... the results are quite different from NickOfTime's 290X results, the 290 should be not much slower than it's X version..[/QUOTE]

Well, mine are XFX 290x Double Dissipation (PCIEx 16x) running around 66 - 70C so there is no throttling...
Hmm, it probably is the Catalyst Version, since opencl is compiled at runtime ,there is a lot of variations of performance diffs there, I am using 14.3

Attached results for [URL="http://www.sapphiretech.com/presentation/product/?cid=1&gid=3&sgid=1227&pid=2091&psn=&lid=1&leg=0"]Sapphire R9 290 Tri-X OC[/URL]. As a bonus I've put also log from GPU-Z for entire run :smile:

[QUOTE=kracker;386593]Something's quite wrong there... the results are quite different from NickOfTime's 290X results, the 290 should be not much slower than it's X version..[/QUOTE]

Hmm i don't really know where is problem. I run mfakto on Catalyst 14.4 and 14.9 - results are practically the same.

My plaftorm is 6 years old Asus P5K pro and Xeon E5440 2,83 GHz, which is overclocked to 3,7 GHz. FSB default is 333 MHz and now is set to 443 MHz. It might cause the problem?

[QUOTE=AK76;386651]Hmm i don't really know where is problem. I run mfakto on Catalyst 14.4 and 14.9 - results are practically the same.

My plaftorm is 6 years old Asus P5K pro and Xeon E5440 2,83 GHz, which is overclocked to 3,7 GHz. FSB default is 333 MHz and now is set to 443 MHz. It might cause the problem?[/QUOTE]
Hmm... how are your thermals?

On another note, I've ordered a R9 285... :smile: Will have results by Tuesday/Wednesday.

[QUOTE=Cruelty;386635]Attached results for [URL="http://www.sapphiretech.com/presentation/product/?cid=1&gid=3&sgid=1227&pid=2091&psn=&lid=1&leg=0"]Sapphire R9 290 Tri-X OC[/URL]. As a bonus I've put also log from GPU-Z for entire run :smile:[/QUOTE]

Nice! :smile: Well, here's comparing your 290 with AK76's 290... something's wrong.

[code]
5. GPU tf kernels, exponent=66362159 ... calibrating
5. GPU tf kernels, exponent=66362159, 12287M FCs each
k=2223766598517, 0.900843 GHz-days (assignment), 0.025120 GHz-days (per test)
cl_barrett32_79_gs [64-79]: 3609.79 ms ==> 3569.43M FCs/s ==> 601.23 GHz-days/day
cl_barrett32_77_gs [64-77]: 3230.19 ms ==> 3988.90M FCs/s ==> 671.89 GHz-days/day
cl_barrett32_76_gs [64-76]: 3097.96 ms ==> 4159.15M FCs/s ==> 700.57 GHz-days/day
cl_barrett32_92_gs [65-92]: 5107.85 ms ==> 2522.57M FCs/s ==> 424.90 GHz-days/day
cl_barrett32_88_gs [65-88]: 3778.44 ms ==> 3410.12M FCs/s ==> 574.40 GHz-days/day
cl_barrett32_87_gs [65-87]: 3610.30 ms ==> 3568.93M FCs/s ==> 601.15 GHz-days/day
cl_barrett15_73_gs [60-73]: 3728.22 ms ==> 3456.05M FCs/s ==> 582.14 GHz-days/day
cl_barrett15_69_gs [60-69]: 3141.44 ms ==> 4101.59M FCs/s ==> 690.87 GHz-days/day
cl_barrett15_70_gs [60-69]: 3145.50 ms ==> 4096.30M FCs/s ==> 689.98 GHz-days/day
[/code][code]
5. GPU tf kernels, exponent=66362159 ... calibrating
5. GPU tf kernels, exponent=66362159, 6143M FCs each
k=2223766598517, 0.900843 GHz-days (assignment), 0.012560 GHz-days (per test)
cl_barrett32_79_gs [64-79]: 2755.63 ms ==> 2337.92M FCs/s ==> 393.80 GHz-days/day
cl_barrett32_77_gs [64-77]: 2554.79 ms ==> 2521.71M FCs/s ==> 424.76 GHz-days/day
cl_barrett32_76_gs [64-76]: 2486.19 ms ==> 2591.30M FCs/s ==> 436.48 GHz-days/day
cl_barrett32_92_gs [65-92]: 3022.35 ms ==> 2131.60M FCs/s ==> 359.05 GHz-days/day
cl_barrett32_88_gs [65-88]: 2844.33 ms ==> 2265.02M FCs/s ==> 381.52 GHz-days/day
cl_barrett32_87_gs [65-87]: 2756.18 ms ==> 2337.46M FCs/s ==> 393.72 GHz-days/day
cl_barrett15_73_gs [60-73]: 2815.09 ms ==> 2288.54M FCs/s ==> 385.48 GHz-days/day
cl_barrett15_69_gs [60-69]: 2507.41 ms ==> 2569.36M FCs/s ==> 432.78 GHz-days/day
cl_barrett15_70_gs [60-69]: 2508.61 ms ==> 2568.14M FCs/s ==> 432.58 GHz-days/day
[/code]