JerWA Prince


Joined: 01 Jan 2007 Posts: 1497 Location: WA, USA
|
Posted: Sat Jun 27, 2009 3:50 am Post subject: |
|
|
Ok, 6.4.7 finally ran into a problem, but it was the one I expected at least. As verified in my \ProgramData\BOINC\client_state.xml file (look for short_term and long_term debt), the MilkyWay project worked itself into a "negative debt." In essence, BOINC decided it was getting too much work and stopped requesting more, which resulted in an idle GPU.
The fix is quite easy, and I actually setup a Windows task to run every day to do this for me. Doing this for a normal project would really jack your resource split up, but since MW is the only thing on my GPU it's resource share should really be 100% but the manager isn't smart enough for that yet.
Anywho, here's the magic command (run it from your BOINC install directory or you will need your BOINC client authorization info):
boinccmd --set_debts http://milkyway.cs.rpi.edu/milkyway 0 0
This zeros your MW debt, which should promptly return it to work. It won't be high (or low) priority, so it make take a few minutes for the manager to cycle up a work request and such, but this should "solve" the problem with it no longer requesting work after a certain amount of time (mine made it 3 days). You could, in theory, set the debt values high so it would take longer for them to "bottom out" again but changing debts impacts every project and I can't say what would happen if you tweaked this too far.
Keep in mind the project will immediately start accruing negative debt again because it's running 100% of the time, which the manager finds confusing because it's got resource share with the other apps. If it was smart enough to know it was a GPU app it would realize they aren't sharing time, but you deal with what you've got to work with hehe. So you'll have to reset the debt fairly often.
Update: Stats updated for yesterday and it totally blew the old best out of the water with 74,112. My numbers for the next few days will be off as I'm home gaming and such, but it'll be interesting to see how it does next week now that I'm clearing debts on the project every night.
Update 2: Didn't take very long for it to hit the same issue again! I ran the task manually and tada fixed, so I've changed the automated task now to run every hour.
Update 3: Hit an interesting twist in this plot just now. Because I have n1 set, only 1 MW app gets GPU time, but the manager thinks 2 (or even 3) are "running." Because of this and some weirdness in the manager I ended up with MW stuck, 3 "running" but none getting any actual app time. I changed it to n2 and restarted the manager which got it moving again but it's something I'll have to keep an eye on. _________________
Stats: [BOINC Synergy] - [Free-DC] - [MundayWeb] - [Netsoft] - [All Project Stats] |
|