One way I had found to work around my problem before I tried the regedit was to move wu1 to device 0 and wu0 to device 1. Weird but it worked!???

After that TrdDelay adjustment, it really is running nice and smooth. I think that was it.

Thanks, BilBg.

With my HD 6570, is there a way to run more than one wu on it at the same time by setting some config file and is there any increase in total output/points for doing so? Everything else runs prima now!

 
I run 2 AstroPulse on my HD 6570
(AMD ATI Radeon HD 6570 (NI TURKS) [ASUS EAH6570/DI/1GD3(LP)] - I run it at 800/1050 MHz)

Look for app_config.xml

Amend it to your needs:
http://setiathome.berkeley.edu/forum_thread.php?id=74762


"is there any increase in total output" - to test see here:
http://setiathome.berkeley.edu/forum_thread.php?id=75108&postid=1536704#1536704

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I created this file using notepad, put it in the correct directory but it doesn't work. I guess you can't create a .xml file this way? I'm sure this must be a naïve question, but how do I create this .xml file? Thanks from a newbie. Do you get an improved throughput/points using your 2 astropulse
wu's per gpu's?

<?xml version='1.0' encoding='us-ascii'?>

<app_config>
< app>
< name>setiathome_v7</name>
< gpu_versions>
< gpu_usage>0.50</gpu_usage>
< cpu_usage>0.04</cpu_usage>
< /gpu_versions>
< /app>
< /app_config>

I created this file using notepad, put it in the correct directory but it doesn't work.

<?xml version='1.0' encoding='us-ascii'?>

You used the wrong encoding. When using Notepad to make the file, use ANSI encoding, the default it comes with. Anything else is unnecessary.

And when you say "correct directory", what may that be?

---

...
< /gpu_versions>
< /app>
< /app_config>

And why you have spaces added in tags?

Have to be:
</gpu_versions>
</app>
</app_config>

Get this file and see inside (and use as template to edit):
http://www.arkayn.us/seti/app_config.7z

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Yes! It's working! Thanks!

I can probably tell from my running times if it is worth it or not.

This one is missing the start tag.
Get the file I linked in edit on previous post.

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

The print out of your performance pgm:
0 July 2014 - 14:48:29 Start, devices: 2, device count: 1 (1.00)
10 July 2014 - 14:48:29 Set: MB7_win_x86_SSE_OpenCL_ATi_r1843 , Exe: MB7_win_x86_SSE_OpenCL_ATi_r1843.exe , Parameters: --device %device
10 July 2014 - 14:57:42 Runtime: Device: 1, count: 0, 545 seconds
10 July 2014 - 14:57:42 Device: 1, Count: 0, finished.
10 July 2014 - 14:58:13 Runtime: Device: 0, count: 0, 576 seconds
10 July 2014 - 14:58:13 Device: 0, Count: 0, finished.
--------------------------------------------------------------------------- Results:
Device: 0, device count: 1, average time / count: 576, average time on device: 576 Seconds (9 Minutes, 36 Seconds)
Device: 1, device count: 1, average time / count: 545, average time on device: 545 Seconds (9 Minutes, 5 Seconds)
Next :---------------------------------------------------------------------------
10 July 2014 - 14:58:17 Start, devices: 2, device count: 2 (0.50)
10 July 2014 - 14:58:17 Set: MB7_win_x86_SSE_OpenCL_ATi_r1843 , Exe: MB7_win_x86_SSE_OpenCL_ATi_r1843.exe , Parameters: --device %device
10 July 2014 - 15:16:06 Runtime: Device: 1, count: 0, 1068 seconds
10 July 2014 - 15:16:06 Device: 1, Count: 0, finished.
10 July 2014 - 15:16:06 Runtime: Device: 1, count: 1, 1068 seconds
10 July 2014 - 15:16:06 Device: 1, Count: 1, finished.
10 July 2014 - 15:17:02 Runtime: Device: 0, count: 0, 1124 seconds
10 July 2014 - 15:17:02 Device: 0, Count: 0, finished.
10 July 2014 - 15:17:02 Runtime: Device: 0, count: 1, 1124 seconds
10 July 2014 - 15:17:02 Device: 0, Count: 1, finished.
--------------------------------------------------------------------------- Results:
Device: 0, device count: 2, average time / count: 1124, average time on device: 562 Seconds (9 Minutes, 22 Seconds)
Device: 1, device count: 2, average time / count: 1068, average time on device: 534 Seconds (8 Minutes, 54 Seconds)
Next :---------------------------------------------------------------------------
10 July 2014 - 15:17:04 Start, devices: 2, device count: 3 (0.33)
10 July 2014 - 15:17:04 Set: MB7_win_x86_SSE_OpenCL_ATi_r1843 , Exe: MB7_win_x86_SSE_OpenCL_ATi_r1843.exe , Parameters: --device %device
10 July 2014 - 15:43:21 Runtime: Device: 1, count: 1, 1575 seconds
10 July 2014 - 15:43:21 Device: 1, Count: 1, finished.
10 July 2014 - 15:43:23 Runtime: Device: 1, count: 2, 1577 seconds
10 July 2014 - 15:43:23 Device: 1, Count: 2, finished.
10 July 2014 - 15:43:39 Runtime: Device: 1, count: 0, 1593 seconds
10 July 2014 - 15:43:39 Device: 1, Count: 0, finished.
10 July 2014 - 15:44:55 Runtime: Device: 0, count: 2, 1669 seconds
10 July 2014 - 15:44:55 Device: 0, Count: 2, finished.
10 July 2014 - 15:45:04 Runtime: Device: 0, count: 0, 1678 seconds
10 July 2014 - 15:45:04 Device: 0, Count: 0, finished.
10 July 2014 - 15:45:04 Runtime: Device: 0, count: 1, 1678 seconds
10 July 2014 - 15:45:04 Device: 0, Count: 1, finished.
--------------------------------------------------------------------------- Results:
Device: 0, device count: 3, average time / count: 1675, average time on device: 558 Seconds (9 Minutes, 18 Seconds)
Device: 1, device count: 3, average time / count: 1581, average time on device: 527 Seconds (8 Minutes, 47 Seconds)
Next :---------------------------------------------------------------------------
10 July 2014 - 15:45:07 Start, devices: 2, device count: 4 (0.25)
10 July 2014 - 15:45:07 Set: MB7_win_x86_SSE_OpenCL_ATi_r1843 , Exe: MB7_win_x86_SSE_OpenCL_ATi_r1843.exe , Parameters: --device %device
10 July 2014 - 16:20:20 Runtime: Device: 1, count: 3, 2112 seconds
10 July 2014 - 16:20:20 Device: 1, Count: 3, finished.
10 July 2014 - 16:20:20 Runtime: Device: 1, count: 1, 2112 seconds
10 July 2014 - 16:20:20 Device: 1, Count: 1, finished.
10 July 2014 - 16:20:22 Runtime: Device: 1, count: 0, 2114 seconds
10 July 2014 - 16:20:22 Device: 1, Count: 0, finished.
10 July 2014 - 16:20:24 Runtime: Device: 1, count: 2, 2116 seconds
10 July 2014 - 16:20:24 Device: 1, Count: 2, finished.
10 July 2014 - 16:22:09 Runtime: Device: 0, count: 1, 2221 seconds
10 July 2014 - 16:22:09 Device: 0, Count: 1, finished.
10 July 2014 - 16:22:11 Runtime: Device: 0, count: 2, 2223 seconds
10 July 2014 - 16:22:11 Device: 0, Count: 2, finished.
10 July 2014 - 16:22:11 Runtime: Device: 0, count: 3, 2223 seconds
10 July 2014 - 16:22:11 Device: 0, Count: 3, finished.
10 July 2014 - 16:22:13 Runtime: Device: 0, count: 0, 2225 seconds
10 July 2014 - 16:22:13 Device: 0, Count: 0, finished.
--------------------------------------------------------------------------- Results:
Device: 0, device count: 4, average time / count: 2223, average time on device: 555 Seconds (9 Minutes, 15 Seconds)
Device: 1, device count: 4, average time / count: 2113, average time on device: 528 Seconds (8 Minutes, 48 Seconds)
>> The best average time found: 542 Seconds (9 Minutes, 2 Seconds), with count: 0.33 (3)

I guess the readings are obvious to interpret. The maximum gain is 3.2% At the .33 level. I don't know if that is worth it. I run three pc's but this one is the only one with cards capable of floating point. Most of my calculations for BOINC are done in the cooler months when the AC doesn't need to run OT. Appreciate the help you have given me. I've learned a few things or two.

I have decided to run at .33 wu and claim my 3.2% bonus and see how the rest of my system is affected by this. Before the cooler weather rolls around I will put in a third 6570 gpu or maybe a 7770 and rerun the performance pgm. Thanks again for all the help.

The print out of your performance pgm

The package you used is made/collected by me but the program itself is not mine.

SetiPerformance is by eFMer (Fred Melgert):
http://efmer.com/forum/index.php?topic=974.0
http://setiathome.berkeley.edu/show_user.php?userid=8906489

eFMer also makes other great programs which I use (TThrottle, BoincTasks)
http://www.efmer.com/b/

10 July 2014 - 14:48:29 Set: MB7_win_x86_SSE_OpenCL_ATi_r1843 , Exe: MB7_win_x86_SSE_OpenCL_ATi_r1843.exe

For AMD Radeon HD 6570 you should use (in the test and Lunatics' Installer):
MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe

It gives 10-20% faster times.

I have decided to run at .33

If you feel too much lag (using the Windows Desktop) make it 0.5


*** P.S.

My AMD Radeon HD 6570 [ASUS EAH6570/DI/1GD3(LP)] was very easy to Overclock

It runs stable at 800/1050 MHz (GPU/DDR3) with no voltage change (which is not possible on my card)
GPU temperature in hot summer (30°C in the room) at full load do not exceed 55°C

The only program that manages to heat the GPU >70°C is OCCT 3.1.0 (but not the later versions OCCT 4.x)
Five versions of FurMark (1.8.2 ... 1.13.0) do not push it over 65°C


For the overclock I use MSI Afterburner 2.2.4 (I didn't tested newer versions)
http://event.msi.com/vga/afterburner/download.htm

MSI Afterburner 2.2.4 (not available anymore on msi.com - file from pc-driverdown is the same as the one I have from msi.com since 12.10.2012)
http://www.pc-driverdown.com/msi-afterburner-2-2-4-windows-vista7xp/
Direct link: http://down3.driversdown.com/Bios/MSIAfterburnerSetup224.zip

(another feature of MSI Afterburner is it makes great video capture (MJPG) from games)

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I tried the HD5 before and it didn't work but now it works.

I tried overclocking with catalyst control ctr twice and it failed and crashed my system. I have two XFX gpu's, can I use the msi overclocker with XFX? Isn't MSI a maker of it's own cards?

Really appreciate the help. Soon I might be out of questions. :-)

Net Increase from switch to "HD5" =19%! WOW! I didn't try to run at .25.
Thanks again.

Starting test: (MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843)
11 July 2014 - 15:58:48 Start, devices: 2, device count: 3 (0.33)
11 July 2014 - 15:58:48 Set: MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843 , Exe: MB7_win_x86_SSE_OpenCL_ATi_HD5_r1843.exe , Parameters: --device %device
11 July 2014 - 16:20:10 Runtime: Device: 1, count: 1, 1281 seconds
11 July 2014 - 16:20:10 Device: 1, Count: 1, finished.
11 July 2014 - 16:20:11 Runtime: Device: 1, count: 0, 1282 seconds
11 July 2014 - 16:20:11 Device: 1, Count: 0, finished.
11 July 2014 - 16:20:13 Runtime: Device: 1, count: 2, 1284 seconds
11 July 2014 - 16:20:13 Device: 1, Count: 2, finished.
11 July 2014 - 16:21:19 Runtime: Device: 0, count: 0, 1350 seconds
11 July 2014 - 16:21:19 Device: 0, Count: 0, finished.
11 July 2014 - 16:21:23 Runtime: Device: 0, count: 1, 1354 seconds
11 July 2014 - 16:21:23 Device: 0, Count: 1, finished.
11 July 2014 - 16:21:24 Runtime: Device: 0, count: 2, 1355 seconds
11 July 2014 - 16:21:24 Device: 0, Count: 2, finished.
--------------------------------------------------------------------------- Results:
Device: 0, device count: 3, average time / count: 1353, average time on device: 451 Seconds (7 Minutes, 31 Seconds)
Device: 1, device count: 3, average time / count: 1282, average time on device: 427 Seconds (7 Minutes, 7 Seconds)

 
MSI and EVGA are makers of their own cards.

But MSI Afterburner and EVGA Precision work on every card (as you see I have ASUS EAH6570/DI/1GD3(LP))
I am inclined to believe (without proof) that this is demanded by the (Russian) programmer.

MSI Afterburner and EVGA Precision are based on RivaTuner (my post from 2011 with screenshots):
http://setiathome.berkeley.edu/forum_thread.php?id=65894&postid=1165854#1165854

Read the short "Interview: Alex 'Unwinder' / RivaTuner":
http://setiathome.berkeley.edu/forum_thread.php?id=65894&postid=1165516#1165516

The RivaTuner files are used by both tools:
http://prikachi.com/images/327/3969327T.png

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I'm running the msi overclocker. I first set it to 500 MHz for the core clock and it crashed my system. Right now I have it set at 407MHz core and 450MHz memory and it has been working right for 15-20 minutes at 52 degrees C. and 48 degrees C. which is about 2 degrees higher than when I ran it without overclocking. I don't want to push it to where I will shorten the life of the cards by any appreciable amount. Sometimes when you need an older card replacement they try and stick it to you. I'll keep testing and see what happens. Cheers!

 
Strange!

The default for AMD Radeon HD 6570 is 650 MHz for GPU and 900 MHz for DDR3 RAM (and higher for DDR5)
http://www.amd.com/en-gb/products/graphics/desktop/6000/6570#2
http://en.wikipedia.org/wiki/Radeon_HD_6000_Series#Northern_Islands_.28HD_6xxx.29_Series

MSI Afterburner have button Reset which should set the defaults.

The way it looks for me (Overclocked):



 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

My core clock on msi is showing 400 min and 650 max. I think I have the cheap XFX version.

 
What happens when you press button Reset in MSI Afterburner ?
(what core/memory MHz it sets)

There seem to be only 3 cards with this chip:
http://xfxforce.com/en-us/products/all-previous-gpus#*

... and only one with 1GB RAM which have to be your model:
http://xfxforce.com/en-us/products/all-previous-gpus/amd-radeon-hd-6570-core-edition-hd-657x-zdf2

650 MHz Core Clock
1GB 64-Bit DDR3
1000 MHz Effective Memory Clock

These have to be the defaults (it's normal when the GPU is idle to have much lower MHz, but at load it have to switch to the above values)
Why 650 MHz is the max in MSI Afterburner I don't know

! Make sure that in Catalyst Control Center - AMD Overdrive you do NOT apply any Overclock (else they will fight with MSI Afterburner)

My is grayed-out as I never used it (by clicking the golden-key icon):



 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)