First, you must mean "similar" work unit; it's impossible to run the "same" workunit on your system twice.

Second, I'm curious as to how you arrived at this assumption, given that there are only 5 pending WU's and one valid WU on your two machines that have ATI cards, and all those were processed with the CPU.

I have to assume that he is pointing to his laptop pc. That has a APU where the CPU and GPU are on the same chip and share resources. the GPU will not be very fast. It may be about as fast or as slow as your CPU WU's
____________
In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

I have to assume that he is pointing to his laptop pc. That has a APU where the CPU and GPU are on the same chip and share resources. the GPU will not be very fast. It may be about as fast or as slow as your CPU WU's

I was afraid of that. I thought this ATI was good for crunching but i was wrong.

Did you get some performance per $ invested or some performance per watt estimation or your conclusion based exclusively on BOINC time to complete estimates that have nothing near to reality with first few tasks???

ATi as good crunching device as others are. It can be disputed what better or worser only after comparison measure established. Good in one measure can be bad in some another one, btw.

And about 68C - it's quite low temp for C-60. It feels quite good at 80C too.

I crunch on C-60 netbook almost year already and can say that this APU device definitely faster than my prev Atom based one. And its GPU part faster in SETI (both AP and MB apps) that it's 2 CPU cores part. In performance per invested $ measure it's better. Would it be better in performance per watt measure? Maybe, but can't give answer cause did not checked it.
So, be carefull with conclusions based on quite little experience.

The first AP unit I got for my AMD 6670 1GB card (5 days ago) was puzzling. It ran at ~0% GPU load and took something like 24 hours to finish. The load graph showed bumps up to maybe 10% every few minutes.

Long story short, I discovered if I set unroll 8, ffa_block 16384, and ffa_block_fetch 8192 the AP units run at 85% and a typical run time for the 20 or so I've completed is 1.5 hours.

I didn't expect I'd have to tweak the stock app, but in my case I definitely had to to basically make it work at all.

I can tell you what I did, I'm hardly the expert. Raistmer is, he wrote the code in case you didn't know.

I'm running win 7, so in C:\ProgramData\BOINC\projects\setiathome.berkeley.edu there is a file called ap_cmdline_6.04_windows_intelx86__opencl_ati.txt. You can use that file to set parameters for the Astropulse app when it starts up. That's the first thing I know. I'll give an example of how to type the values into that file later on.

The second thing I know is the three parameters I've seen talked about: -unroll, -ffa_block, and -ffa_block_fetch. Of those three, unroll is most important. The first thing I did was adjust that one so I got the GPU load up off the floor.

Question is, what value to use? Again from poking around I got the impression it should be set in relation to how many compute units the GPU has. How do you find *that* out? Well, I looked in the stderr.txt file for a running Astropulse job. Where is that? C:\ProgramData\BOINC\slots\<number> where <number> is some small integer like 0, 1, 2. One of those slots will be for the Astropulse job, you just have to look in each one for files that look like they belong to Astropulse. Problem is, if there is no running job, there is no slot.

I found from stderr.txt I have 6 compute units. If you can't find out how many you have maybe just start increasing unroll from the default value which is 2 until you find a value that works well.

So here is how to set unroll, open that file from paragraph 2 with notepad and type "-unroll 3" without the quotes. Use 3 or whatever value you are trying out. Then save.

Boy this is getting long. Ok so next, I would test it on a running AP job (probably not the professional way of doing it) by suspending the whole SETI@home project from BOINC then resuming it. That restarts all your jobs including Astropulse which will pick up your new parameters. Then look at your GPU load using GPUZ (free download) or Catalyst Control Center to see if it's any better. I ended up using 8, which is 2 more than my number of compute units.

The other two parameters affect how much video memory your job uses. I'm not sure but if you set them too high you might crash the job. The defaults are -ffa_block 1024 -ffa_block_fetch 512. What you should do is make sure ffa_block is always twice ffa_block_fetch and then increase them by factors of two so first I'd try -ffa_block 2048 -ffa_block_fetch 1024 and so forth.

So your parameters file would look like, for example

-unroll 4 -ffa_block 2048 -ffa_block_fetch 1024

GPUZ will tell you how much memory your job is using, if you know what the limit is you can stop increasing the ffa's before you exceed it. Otherwise, maybe don't mess with them because they are secondary in importance after -unroll. You can just have a file that sets unroll and the other parameters will take their defaults.

As I said, that's what I did based on reading the message boards and it seems to work for me, but I'm not the expert.

1. No, it would not, MB app uses different set of params to tune.
2. C-60 is low end GPU so it should work quite good with stock defaults (for AP). Or you trying to speedup your secondary ATi cruncher, HD5xxx based one ?
3. Cause you said you run not AP but "SETI" (MB, i.e. MultiBeam, perhaps) you running with app_info, not stock.

I see no completed GPU tasks for C-60 host but few for HD5xxx host.
From stderr:

Number of period iterations for PulseFind setted to:20
Number of app instances per device setted to:1

you could try to set number of instances to 2 for app and decrease number of iterations (if not experience GUI lags).

All this can be done via <cmdline> field in app_info.xml file for MultiBeam app.
<cmdline>-instances_per_device 2 -period_iterations_num 10</cmdline>
Also, <count>0.5</count> should be used for r390 of MultiBeam app you running if you want to run 2 instances at once.

1. No, it would not, MB app uses different set of params to tune.
2. C-60 is low end GPU so it should work quite good with stock defaults (for AP). Or you trying to speedup your secondary ATi cruncher, HD5xxx based one ?
3. Cause you said you run not AP but "SETI" (MB, i.e. MultiBeam, perhaps) you running with app_info, not stock.

I see no completed GPU tasks for C-60 host but few for HD5xxx host.
From stderr:

Number of period iterations for PulseFind setted to:20
Number of app instances per device setted to:1

you could try to set number of instances to 2 for app and decrease number of iterations (if not experience GUI lags).

All this can be done via <cmdline> field in app_info.xml file for MultiBeam app.
<cmdline>-instances_per_device 2 -period_iterations_num 10</cmdline>
Also, <count>0.5</count> should be used for r390 of MultiBeam app you running if you want to run 2 instances at once.

What happens increasing the period iterations?
____________
By your command !!!