Posts by Hans-Ulrich Hugi

1) Message boards : Number crunching : R9 290 (Message 62239) Posted 31 Aug 2014 by Hans-Ulrich Hugi Post: My R290 (Sapphire Tri-X) also does not work. The "APP" stuff doesn't help. Is there anybody around whos R290 (x) is working in MilkyWay?
2) Message boards : Number crunching : Server oopsie?? (Message 45503) Posted 12 Jan 2011 by Hans-Ulrich Hugi Post: No new work is sent out. I guess that's what he means.
3) Message boards : Number crunching : HD5870 (Message 32719) Posted 25 Oct 2009 by Hans-Ulrich Hugi Post: @verstapp Catalyst 9.10 drivers for WinXP support the 58x0 series. Only the 57x0 cards are yet unsupported. But (at least me) i'm still suffering a lot of VPU recovery under WinXp with 4870 and 5870 - this does not happen under Vista32/64 or Win7 64.
4) Message boards : Number crunching : HD5870 (Message 31971) Posted 4 Oct 2009 by Hans-Ulrich Hugi Post: @ExtraTerrestrial Apes The memory clocks are misread. Probably you noticed that it always reads 300 MHz, if the card runs at 1200 or 1320 MHz. But GPU-Z shows the correct speed. And the 5870 correctly reduces the memory/gpu clocks after about 5 seconds on idle.
5) Message boards : Number crunching : HD5870 (Message 31959) Posted 4 Oct 2009 by Hans-Ulrich Hugi Post: Today i did some testing with the 5870 at different clock speeds (Milkyway and Collatz). All results are under Win7 Ultimate 64bit (Build 7600) with a Q9650 @ 3.75 GHz, Boinc Client 6.10.11 and the 0.20 Milkyway SW (no command line parameters changed). Under Collatz higher clocks greatly improve the performance (see my post there). Here are the results for Milkyway: Clocks 850 / 1200 (@stock) =========================== GPU load max. 99% (GPU-Z 0.3.5) GPU core clock: 850 MHz, memory clock: 300 MHz (Wrong: 1200 MHz!) predicted runtime per iteration is 62 ms(33.3333 ms are allowed), dividing each iteration in 2 parts borders of the domains at 0 800 1600 Calculated about 8.22242e+012 floatingpoint ops on GPU, 1.23583e+008 on FPU. Approximate GPU time 20.7792 seconds CPU time: 1.65361 seconds, GPU time: 20.7792 seconds, wall clock time: 21.793 seconds, CPU frequency: 3.7371 GHz CPU time: 1.70041 seconds, GPU time: 20.7948 seconds, wall clock time: 21.833 seconds, CPU frequency: 3.7371 GHz CPU time: 1.71601 seconds, GPU time: 20.7792 seconds, wall clock time: 21.844 seconds, CPU frequency: 3.7371 GHz Clocks 850 / 1320 (GPU @stock / Memory + 10%) ============================================= GPU load max. 99% (GPU-Z 0.3.5) GPU core clock: 850 MHz, memory clock: 300 MHz (Wrong: 1320 MHz!) predicted runtime per iteration is 62 ms(33.3333 ms are allowed), dividing each iteration in 2 parts borders of the domains at 0 800 1600 Calculated about 8.22242e+012 floatingpoint ops on GPU, 1.23583e+008 on FPU. Approximate GPU time 20.7636 seconds CPU time: 1.66921 seconds, GPU time: 20.7636 seconds, wall clock time: 21.831 seconds, CPU frequency: 3.7371 GHz CPU time: 1.70041 seconds, GPU time: 20.8104 seconds, wall clock time: 21.907 seconds, CPU frequency: 3.7371 GHz CPU time: 1.70041 seconds, GPU time: 20.8104 seconds, wall clock time: 21.847 seconds, CPU frequency: 3.7371 GHz Clocks 935 / 1200 (GPU + 10% / Memory @stock) ============================================== GPU core clock: 935 MHz, memory clock: 300 MHz (Wrong: 1200 MHz!) predicted runtime per iteration is 56 ms (33.3333 ms are allowed), dividing each iteration in 2 parts borders of the domains at 0 800 1600 Calculated about 8.22242e+012 floatingpoint ops on GPU, 1.23583e+008 on FPU. Approximate GPU time 20.1084 seconds CPU time: 1.01401 seconds, GPU time: 20.1084 seconds, wall clock time: 21.15 seconds, CPU frequency: 3.7371 GHz CPU time: 1.01401 seconds, GPU time: 20.1084 seconds, wall clock time: 21.15 seconds, CPU frequency: 3.7371 GHz CPU time: 1.01401 seconds, GPU time: 20.0928 seconds, wall clock time: 21.125 seconds, CPU frequency: 3.7371 GHz Clocks 935 / 1320 (both + 10%) =============================== GPU load max. 99% (GPU-Z 0.3.5) GPU core clock: 935 MHz, memory clock: 300 MHz (Wrong: 1320MHz!) predicted runtime per iteration is 56 ms(33.3333 ms are allowed), dividing each iteration in 2 parts borders of the domains at 0 800 1600 Calculated about 8.22242e+012 floatingpoint ops on GPU, 1.23583e+008 on FPU. Approximate GPU time 20.0772 seconds CPU time: 1.04521 seconds, GPU time: 20.0772 seconds, wall clock time: 21.144 seconds, CPU frequency: 3.7371 GHz CPU time: 0.998406 seconds, GPU time: 20.0928 seconds, wall clock time: 21.122 seconds, CPU frequency: 3.7371 GHz CPU time: 0.998406 seconds, GPU time: 20.0928 seconds, wall clock time: 21.122 seconds, CPU frequency: 3.7371 GHz I did hope to see a similar improvement with Milkyway as i got it with Collatz. But the result is only a lower CPU time a minimal better GPU time.
6) Message boards : Number crunching : HD5870 (Message 31797) Posted 1 Oct 2009 by Hans-Ulrich Hugi Post: @ Ironwork16 Actually there is no driver for the 58x0 and WinXp from the ATI/AMD website. But with my Asus 5870 i got a cd with a driver for WinXp. This driver works but i believe it is less stable than the driver for Vista/Win7. Crunching unter Win7 is fun with the 5870...