Let's hope! My guess is that the Unraid and Rackspace teams are the ones with the big servers, either the companies themselves or customers or both. Rackspace only shows 22 members but they've popped into the top 10 out of nowhere.I keep seeing all these messages about contributors being out of work. I have never been below a 1000 WUs in progress. Currently, sitting with 1418 in the queue. Am I the one that is sucking them all up? I'm sort of embarrassed. However, if I'm the only one with work, that sort of determines which team finishes first in the challenge
I'm mildly troubled by reports of long running tasks, which are now preferred by the project, giving extremely low credit. I've seen reports of 6 - 8 points for an 8 hour task. I've got a handful of such tasks myself. They'll need to get that fixed if they really want folks to run them 16+ hours. Supposedly they're looking into it.We opened at #6 this morning and now at #4....
One of my machines is starting to run dry but the others probably have a good six hours of work before they start draining down. Maybe there will be more work by then.
I had a few tasks in the queue, I shut off network access when I got home last night. If I'd been thinking I could have done that yesterday. Anyway, that helped a little. I think I'll set SCC as a backup as well.Now moved up to #3 with the last update... Could it be the other team's machines are running dry.
I know that setting the resource share to 0 tells BOINC to get tasks from WCG only when it can't get tasks from any other project. What I have noticed is, I only get enough WCG to keep the threads active. No queue. Regardless of the Attach Every # of Days setting. I don't think a Project preempts another. What I have done is only selected SCC at WCG because they run in less that 2 hours. That way, if Rosetta dumps in a lot of work, the machine will be free of WCG work within 2 hours. If you select ARP or FAH that run in 5 or more hours, you most likely will have to wait for those to finish before Rosetta work starts. It's probably a good thing that Projects don't get suspended as that would just create a bunch of resends at the other project potentially. Once the work is downloaded, the client manages the work based on deadlines, so if you downloaded a lot of FAH from WCG, they would most likely preempt Rosetta as they have a 1 day deadline. That's my best guess...Newbie question. Running WCG on some boxes while waiting for Rosetta tasks. I read somewhere to set share (project weight) for WCG to zero to stop it from hogging resources. My question is, are there any settings to allow a prioritized project to force another project to suspend when tasks are available for the prioritized project? I'm not positive, but a few weeks ago it looked like WCG did that on its own as i was selecting projects to run.