command line option for amd?

-unroll 7 -oclFFT_plan 256 16 256 -ffa_block 4096 -ffa_block_fetch 2048

is the amd command line I am using for a 6570 on MB v7.

Correct or not?

Thanks

---

merle - vote yes for freedom of speech

Make it -unroll 6.

---

With each crime and every kindness we birth our future.

Make it -unroll 6.

Vielen Dank Mike

---

merle - vote yes for freedom of speech

-unroll 7 -oclFFT_plan 256 16 256 -ffa_block 4096 -ffa_block_fetch 2048

is the amd command line I am using for a 6570 on MB v7.

I hope you mean AP v7
MB v7 don't have -unroll ...

---

 


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

-unroll 7 -oclFFT_plan 256 16 256 -ffa_block 4096 -ffa_block_fetch 2048

is the amd command line I am using for a 6570 on MB v7.

I hope you mean AP v7
MB v7 don't have -unroll ...

BilBg,

I mean MB v7 not AP v7.

What would the MB v7 command line look like?


PS. I am not doing AP's anymore. Doesn't work right on the new card.

---

merle - vote yes for freedom of speech

? So you want to put something in:
mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt

Look in:
<BOINC_Data>\projects\setiathome.berkeley.edu\docs\

for:
MultiBeam_OpenCL_ReadMe.txt

to see the available switches

PS. I am not doing AP's anymore. Doesn't work right on the new card.

Every computer can have its own Settings/apps/...

---

 


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

So my mistake.
I also thought you meant AP7.

On MB7 you can only add -sbs 256 to speed things up a little.

---

With each crime and every kindness we birth our future.

So my mistake.
I also thought you meant AP7.

On MB7 you can only add -sbs 256 to speed things up a little.

And period_iterations_num

My mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt has:

-sbs 256 -period_iterations_num 10 -instances_per_device 3

Mine is set to 40 to avoid screen lags.
You are below default.

---

With each crime and every kindness we birth our future.

OK thanks,

I'll use the -sbs 256 part.

I don't have but one instance per device, so I'm not sure if I need the -period... or not. If I need it I'll put in (40+10)/2. A compromise. :-)

---

merle - vote yes for freedom of speech

-period_iterations_num N

: Splits single PulseFind kernel call to N calls for longest PulseFind calls.
Can be used to reduce GUI lags or to prevent driver restarts.
Can affect performance. Experimentation required.
Default value for v6/v7 task is N=20
N should be positive integer.
If you experience screen lags or driver restarts increase -period_iterations_num


On my AMD Radeon HD 6570 - I feel too much Desktop lag even with:
-period_iterations_num 200

... so I don't run MultiBeam on it

If you try -period_iterations_num 10 this will be even more lag than the default

(Sten-Arne: "using 10 and no lag" is for high-end GPU with "compute units: 20"
http://setiathome.berkeley.edu/result.php?resultid=3813645554
)

---

 


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

There is not much speed difference between period_itrerations_num 10 and 200.

On a 6570 it might be noticable.

Sten_Arne told me he dont get screen lags at all.
OTOH it doesn`t hurt using higher values.

---

With each crime and every kindness we birth our future.

OK, thanks again,

I'll watch for the screen lags but so far none at all.
But this 6570 is sometimes temperamental. Just as I was
typing I noticed a little bit of lag.

---

merle - vote yes for freedom of speech

PS. I am not doing AP's anymore. Doesn't work right on the new card.

You could try going back to an older driver and see if that works. I ran the 14.6 Beta version without any trouble for a couple months. After going to 14.9 one card with a small 50MHz OC began producing too many pulses. Changing it back to stock seems to have fixed it. It could be your card is picky about drivers and might work better with a different driver. Going backwards usually requires using the Display Driver Uninstaller because the older Installer will not overwrite newer files. I haven't tried uninstalling 14.9 yet, AMD may have fixed it. You could try uninstalling 14.9 and installing 14.4 and seeing if it uses the correct AMD_App for 14.4. If it doesn't, you'll have to use the Display Driver Uninstaller to remove all of 14.9 and then install 14.4. If that doesn't work you could try the latest Beta Driver...

So with this new release 43a, I am going to try again to use 2 wu's for this device for MB. For this I need both:

a) in cmd line - instances_per_device 2

and

b) app_config of
gpu .5
cpu 1

Sound OK?

---

merle - vote yes for freedom of speech

I'm trying that. It seems to work. I set -period...40 too.

---

merle - vote yes for freedom of speech

PS. I am not doing AP's anymore. Doesn't work right on the new card.

You could try going back to an older driver and see if that works. I ran the 14.6 Beta version without any trouble for a couple months. After going to 14.9 one card with a small 50MHz OC began producing too many pulses. Changing it back to stock seems to have fixed it. It could be your card is picky about drivers and might work better with a different driver. Going backwards usually requires using the Display Driver Uninstaller because the older Installer will not overwrite newer files. I haven't tried uninstalling 14.9 yet, AMD may have fixed it. You could try uninstalling 14.9 and installing 14.4 and seeing if it uses the correct AMD_App for 14.4. If it doesn't, you'll have to use the Display Driver Uninstaller to remove all of 14.9 and then install 14.4. If that doesn't work you could try the latest Beta Driver...

Thanks TBar,
I'm also having a problem with MB using more than 1 wu. It works for awhile then it just stops and only runs 1 again. It uses about 85% of capacity with one wu. Although on some wu's it will occasionally hit 99%. I might try that 14.4 and see if it's better - just not right now.

---

merle - vote yes for freedom of speech

Merle,

What do you mean when you use MB? I use MB to mean mulitbeam (a type of work unit) AP for astropulse and I use MoBo for MotherBoard. Just asking as I'm getting confused trying to read your post.

Zalster

Merle,

What do you mean when you use MB? I use MB to mean mulitbeam (a type of work unit) AP for astropulse and I use MoBo for MotherBoard. Just asking as I'm getting confused trying to read your post.

Zalster

Well, yes I'll have to stop using it like that, sorry. In this thread I was using it in the sense of multibeam. (got myself confused too)

---

merle - vote yes for freedom of speech