Forum > GPU crunching
Can't get CPU work
Jason G:
Now, it seems the powers that be have promoted you, and that you should now be able to visit the beta threads (Now that we know It's all Boinc's fault ::))
Purple Rabbit:
Woo Hoo!
Oops! (collecting himself for proper presentation)
I mean thanks. I can indeed acquire previously forbidden knowledge and will use it for the benefit of the project. I hope that I can be worthy of this honor.
Rick
Purple Rabbit:
It's been almost a month since my last post and I promised to get back with you. I'm still not able to balance the CPU/GPU load within BOINC 6.6.28...sigh. I've tried 6.6.36--Gag! It's even worse than before with the other projects. Maybe I didn't have enough patience? I figured a week would be enough. I'm back to BOINC 6.6.28 (although perhaps not back far enough?)
The Raimaster/Marius scripts have helped a lot, but they still require babysitting. Marius 1.2 still works the best for me, but I'm manually running Marius 1.6 at the moment on a Q6600 with an 8600GTS on Win Vista. As I said before the GPU card is slow (a bit faster than the CPU tho-I consider it an extra processor), but geez, BOINC should know better...sigh.
My "experiment" allowed the STD to get above 50,000 several times. This didn't get me very many (I got one or two) CPU units. At these points I lost patience with BOINC and used the script.
My current procedure when I get up in the morning is to check the STD. If it's humongous (like over 20,000), then suspend the SETI task. SETI STD goes to zero. I then run the script (whatever version I think is best at the time), watch to see if there are changes (sometimes not, so try again with different settings), and resume.
I'm not asking for help anymore. BOINC is as BOINC does...sigh. Any miraculous solutions would be appreciated, however :)
Rick
Richard Haselgrove:
During a recent SETI outage, I joined another project (AQUA) to get CUDA work (and only CUDA work - I explicitly rejected CPU work).
Everything is running fine. CUDA tasks are running FIFO as expected (v6.6.36), CPU tasks are swapping around under Resource Share control. Only thing is, the CUDA-only project has jumped up to STD 77,919, and the CPU tasks are nudging each other up and down around a median of -25,000 ish. Doesn't matter, it all works, but it looks a bit ugly.
Since the CUDA apps don't seems to respect resource share, but it does affect debt, I've now set AQUA to a RS of 1 (others are 100/200/300). Debt seems to be heading back towards neutrality - slowly, but I can wait, since it makes no difference anyway.
Purple Rabbit:
Hmmm, that's a thought. I've been running SETI (my only GPU project) with a various resource of between 10 and 35 on this computer (the other projects (7 of them) are 25, my standard share).
All this started when I wanted to only run a GPU SETI on this computer . The STD got out of hand for SETI and affected the other projects. I never tried 1. VLAR/VHAR kind of complicates matters for SETI, but I really don't mind killing a few tasks as long as there aren't not to many of them (unfortunately I've had a bunch recently...sigh)
My other problem would be as the time to completion approaches 3 minutes (CPU time for the GPU-normally 40 to 50 minutes wall clock time for the GPU and 75 to 90 minutes wall clock time for the CPU) I tend to get a tremendous number of tasks running the GPU only...sigh. It looks like I have to run a CPU task at least occasionally to keep the number up. Again, this requires baby sitting the tasks.
Navigation
[0] Message Index
[*] Previous page
Go to full version