First CUDA Unit done!

16/01/2009 9:58:36 PM|SETI@home|Starting task 07no08aa.20143.16023.11.8.166_1 using setiathome_enhanced version 607

16/01/2009 10:21:31 PM|SETI@home|Computation for task 07no08aa.20143.16023.11.8.166_1 finished

So that took 22 mins and 55 sec which I believe would have taken about 2.5 hrs on my system with my CPU.

What I noticed on this is that it took about 18 min to get to 50% complete, but than the remaining 50% completed in 3 mins. Not sure why that happened.

If anyone is interested to see the TaskID details http://setiathome.berkeley.edu/result.php?resultid=1124520917

Now what I found strange was that as soon as my system finished this CUDA WU BOINC downloaded another WU, which was an AstroPulse. Instead of it putting the unit in a Ready to Start State, it started running the WU. Now I should tell you that my system on the initial start up already grabbed 2 AP's and they are already running. I only have a dual core CPU, but I did use the modified cc_config.xml file like it was suggested so that both my CPU and GPU can be running at the same time.

<cc_config>
<options>
<ncpus>3</ncpus>
</options>
</cc_config>

that's what I have in the file, which I've understood to be correct. If it's wrong please let me know. It may be a bug with the new 6.6.0 BOINC manager possibly because initially it was only running 2 CPU WU's (mind you BOINC only had downloaded 2 to begin with. So maybe I don't need the modified cc_config file.

Thanks
Vager

---

that's what I have in the file, which I've understood to be correct. If it's wrong please let me know. It may be a bug with the new 6.6.0 BOINC manager possibly because initially it was only running 2 CPU WU's (mind you BOINC only had downloaded 2 to begin with. So maybe I don't need the modified cc_config file.

Thanks
Vager

That cc config file was a work around when using Boinc 6.4.5 and was no longer supposed to be needed when 6.5.0 was introduced.

Edit: Question of my own for anyone that may know, is it recommended for folks using CUDA to be using 6.5.0 or 6.6.0 or does it matter if we stay with 6.4.5?

---

I stay on 6.4.5 with cc_config.
I've selected no AP-units in my prevs so i dont have problems to get cuda-wu's.
My cpu-cores are crunching einstein wu's ;)

---