TBar, I believe

In ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt

I have this setting;
-unroll 18 -ffa_block 4096 -ffa_block_fetch 2048 -sbs 256


With the r7 265 and the 7770, the r7 is at about 79-91% utilization with the 7770 at 31%. How far should I push -unroll? Go beyond -unroll 18? Safely?


Fearful :-)

TBar,

I changed it to unroll -20 and I got erratic behavior from the r7 and then the wu seemed to hang so I aborted it.

By erratic I mean utilization continually bouncing around 98 0 10 0 0 10 98, etc. for maybe 5 minutes.

So I guess I answered my own question.??

TBar, I believe

In ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt

I have this setting;
-unroll 18 -ffa_block 4096 -ffa_block_fetch 2048 -sbs 256


With the r7 265 and the 7770, the r7 is at about 79-91% utilization with the 7770 at 31%. How far should I push -unroll? Go beyond -unroll 18? Safely?


Fearful :-)

With that amount of load on the 7770 it may have been processing a heavily blanked task at the time. In Task Manager you will see one of the GPU apps using more CPU time when this is happening. If that is the case. You can either wait for the task to complete or suspend seeing what another task will do.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

After the -unroll 20 change:
It went spastic.
Then yes, I suspended it and another task worked fine. When I went back to the old task and let it work for awhile, it went spastic again so I aborted it.

TBar,

I changed it to unroll -20 and I got erratic behavior from the r7 and then the wu seemed to hang so I aborted it.

By erratic I mean utilization continually bouncing around 98 0 10 0 0 10 98, etc. for maybe 5 minutes.

So I guess I answered my own question.??

This is the Blanked task you aborted, http://setiathome.berkeley.edu/result.php?resultid=3729451369

Run time	3 hours 7 min 19 sec
CPU time	2 hours 4 min 39 sec
### Restart at 95.50 percent.

It was almost finished. I think I mentioned Blanked tasks, that you can't judge settings while running one. As you noted, the GPU usage is up and down because it is switching the blanked parts off to the CPU. I've also seen one of those tasks appear to be frozen for an hour then suddenly finish in a few minutes. You can easily see blanked tasks in the SIV Window 'BOINC Status'.

An unroll of 18 will most probably have your 7770 topped out on an Unblanked task. Going any higher may introduce detection Errors/Inconclusives/Invalids without providing any gains.

Soon, AstroPulse Version 7.04 will be released on Main solving the Problem with AP Blanking, Astropulse 7.00 released...

OK, I misunderstood. I thought you said increase unroll until the 7770 gets to around 95-98% (period). I need to check blanking. The thing is I have never seen one like this, just going wild with quickly changing utilization percentages. Now I'll know to check the 'records' before I abort it even if it's a spaz. :-) I won't go over 18 either.

Thanks