Forum > GPU crunching

V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use

<< < (49/80) > >>

MaGNeT:
@ Raistmer

I got a 9800GTX+ today for experimenting purposes and found this topic.
Installed the V10 with the update and it looks like everything is working great.

Will let you know in a few days (or earlier) if I encounter any problems.

Great work!

elec999:
I am a few computition errors once in a while, but overall is going strong.
Thank you

k6xt:
I came to grips, internally, with AP vs SETI vs MB work. After reading in the SETI boards that someone had success manually managing the division of work I stopped AP WU downloads temporarily . Sorry I don't recall where, was reading a lot. Its working for me.

Why I post is for this interesting factoid which I have not seen elsewhere. Temporarily I halted inprogress AP until one core switched to SETI and began processing. It seems it was a CUDA unit. After a time I restarted AP processing..lo and behold! The CUDA unit continued processing, albeit very slowly such that for a time the BOINC tasks tab timer was increasing rather than decreasing.

This is probably not a good thing and I won't do it again. My result does not match wingman, and a second wingman is now processing. I'm sure I will lose credit. I believe this is the result:

http://setiathome.berkeley.edu/workunit.php?wuid=424562219

The good news viz AP is patience is a virtue. I've completed about 30 AP WU which have finally begun to verify. V10 is calculating these at ~12 hr per WU. After shutting off further AP download I finally got some SETI which will begin to process tomorrow as the AP cache empties.

If the gurus have a better way to manage work I am all ears. It could be, if I was patient enough, the work would manage itself as the SETI WU return deadline gets near such that BOINC would prioritize them. The trick seems, if some SETI WU are desired, to occasionally manually disable AP downloads, let the cache empty. OTOH I read a blog by Matt Lebofsky implying the reason we got lots of AP recently has to do with differences in AP vs SETI server queue distribution, such that it will eventually manage itself. I wish I'd recorded where I read that on the SETI boards.

Finally, rummaging through the several xml files I noticed that both SETI and BOINC have "Maintain this minimum work" and "Maintain that extra days work" with min set to 0.1 days (or maybe 0.01 I forget) and of course the max of 10 days. I have now set these both to 5 days, i.e. maintain 5 days min and 5 days additional is how the xml states it. I know not, TBA, if this is useful - just did it this AM. Could not find enlightenment on the boards. Some posters have expressed dismay at 10 days cached work. Out here in southwest Colorado USA flyover country we lose power, internet access, and both such that 10 days can be a minimum during stormy season which is fast approaching.

Searching the boards is one time consuming, albeit productive, activity for those of us who are not in the guru category, although fully capable of adding 2 and 2. Occasionally a succinct summary of current events, functionality, expectations etc would be very useful troubleshooting to compare what we SHOULD see vs. what we DO see.

V10 is working for me! Profuse thanks to those who built it.
Art

petefan:
Hi guys....

I read page one and just installed V10 (the third one) for a P4 + one 8500GT (driver 182.08) to see the effect....
My BOINCMGR version is 6.6.11, OS XP SP3 x86.
The CPU is not crunching at all, the process AK_v8b_win_SSE3_GPU_CPU_team_V10 is idle.
BOINCMGR shows "No work available for the applications you have selected. Please check your settings on the web site."
This is my cc_config.xml:
<cc_config>
<options>
<ncpus>2</ncpus>
</options>
</cc_config>


How may I correct this problem? :P

This is a test (taste) for this new app I came across, I am so willing to use this app for all my computers with GTX295 ;D to get higher RAC!!

So many thanks!! ::)

Peter.

Devaster:
it seems that team mod is not needed for SETI main - if u install 6.6.15 and above it will use CPU for SETIMB too

Navigation

[0] Message Index

[#] Next page

[*] Previous page