Two Questions

Question 1, with comment
Yesterday my HD5850 was crunching 1 WU at a time and the 40 to 60 completed results, recently returned, were almost 80% validated.

The other 20% showed up as Completed, waiting for validation, and the wingman cleared this usually pretty quickly.

Observation
Just looking at the same results today, the position are completely different in the work marked Completed, waiting for validation is nearly at 100%, and not cleared until the wingman reports (hopefully soon).

I have noted, after looking back to over 500 returned results, that there is no invalid results returned.

Question 2

I am running the Milkyway 0.23 anonymous platform using <astronomy_0.23_AI_SSE> client.

It is normally assumed that the anonymous platform defaults to 3 WUs at any one time, and for lower crunching numbers that the appl_info file needed to be amened.

I have just used the value <cmdline>n2</cmdline> and restarted BOINC Manager. Unfortunately filling all the <cmdline> attributed still gives 1 WU crunching-at-time.

I also tried dropping the lines -

<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>

To read -

<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>

Without an increase in the number of Milkyway WUs being crunched (still 1).

Can anyone suggest alternatives I can try to increase the active crunching to 2 WUs at-a-time?


Perhaps it would be better to reset the project, or detach and reattach, to use the correct GPU client - the <MilkyWay@Home v0.23 (ati13ati)>?

---

Go away, I was asleep

Shouldn't you be using the astronomy_0.23_ATI_x64.exe application. That sse app is the optimized CPU aplication not the gpu one, so you would be using the stock GPU app.

Shouldn't you be using the astronomy_0.23_ATI_x64.exe application. That sse app is the optimized CPU aplication not the gpu one, so you would be using the stock GPU app.

Would be difficult to run the 64bit application on 32bit WinXP ;). There is also a SSE2 version of the 32bit ATI application. I guess John Clark uses this one.

@John Clark:
To crunch 2 WUs at once, one shouldn't set any command line parameters (the n parameter is deprecated with BOINC 6.10.x clients). Setting
<count>0.5</count>
does the trick, but be sure to set it for both occurences in the app_info.xml. If you just switched the versions, BOINC still uses the settings for the old version.

Thanks

I thought I had tried that on both occurrences, but I must have been mistaken

---

Go away, I was asleep