Sorting the Wheat from the Chaff has always been a difficult & laborious process.

So? What's the best response to that (very real) problem?

Recruit some knowledgeable volunteer Wheat/Chaff sorters, and give them the tools to undertake the task?

Or throw everything - Wheat and Chaff alike - onto the rubbish tip?

I'd be a big job for just one person when things get hectic, but if there's more than one they'd need to co-ordinate with each other so they're not reporting the same thing, and missing others.

But it would be good if a couple of people that are in contact with the staff directly were able to give them a summary of what the discussion is about, and a copy the more usefull/informative posts, considering how quickly things get burried amongst the noise.
If it gets used it gets used, if not *shrug*. Once they've got the information, it's up to them to prioritise things.

---

Grant
Darwin NT

Hello everyone. After return to work on SETI @ Home this week I noticed that the graphics suddenly ceased to function after starting work at WU 05no09af.22632.4980.11.10.168, received on 07/06/2010. I am currently running Seti @ home Enhanced 6.03. There has been no change in equipment or software in a few days ago ... there will be some problem with the program? or does it have something to do with the type of WU?
Thanks.

---

I see people mentioning a 5 work unit per CPU limit but isn't that going to starve the mega crunchers?

Nope. They'll still get work, just not be able to build up their cache while the limit is in place.

Is this new per CPU quota get kicked up as we get closer to the outage?

That's what many have suggested. At this stage the limit stays in place over the weekend & then come Monday it's removed. But all things are subject to change.

Is this some measure to prevent orphan work units from systems that fetch 20 days worth then are never seen again or have some catastrophic hardware problem?

Has been for years, although it gets tweaked occasionally.

---

Grant
Darwin NT

Is this new per CPU quota get kicked up as we get closer to the outage?

That's what many have suggested. At this stage the limit stays in place over the weekend & then come Monday it's removed. But all things are subject to change.

I just got 10 new WUs and have 150 now, guess they may have started raising the limit slowly.

Good evening.

Is this where I post issues with downloading CUDA job packets? My first attempt at CUDA processing since upgrading from MSI 8600GT to a EVA GTX480. The work unit hangs at 4.41% 0.53/11.90MB and appears to start to create 19 tasks. Tried aborting and retying, but to no available. I want to see if is just a bad packet, but no way to move on. I have a bunch of CPU SETI, but the whole idea of the GTX480 was for BOINC GPU processing.

File is named cufft32_30_14.dll. I'd really like to get it running and see what the baby can do.

From message log - Temporarily failed download of cufft32_30_14.dll: HTTP error.

Any ideas or some other board I should post to?

Thanks and have a good day.

Rich

The task limit is somewhat annoying, but I wouldn't be close to running out of work if it were actually 20 (or is the new limit now 5 as a post below suggests) and the website was accurate about what I have returned. One machine (ES-1) keeps hitting the limit in asking for new work, but has only 12 work units. The website shows it has 28 outstanding, however, so something is wildly off. Is it taking a while for work units returned in today's large burst to get updated? The only other computer I checked is being denied with 15 work units, but at least the website shows only that many outstanding for it. Is anyone else seeing problems like this?
Ed

---

ensmail01@verizon.net

Good evening.

Is this where I post issues with downloading CUDA job packets? My first attempt at CUDA processing since upgrading from MSI 8600GT to a EVA GTX480. The work unit hangs at 4.41% 0.53/11.90MB and appears to start to create 19 tasks. Tried aborting and retying, but to no available. I want to see if is just a bad packet, but no way to move on. I have a bunch of CPU SETI, but the whole idea of the GTX480 was for BOINC GPU processing.

File is named cufft32_30_14.dll. I'd really like to get it running and see what the baby can do.

From message log - Temporarily failed download of cufft32_30_14.dll: HTTP error.

Any ideas or some other board I should post to?

Thanks and have a good day.

Rich

Good evening and welcome to the boards !

Since I don't have fermi card (yet), I can only recommend that you read Richard Haselgrove's sticky thread just few clicks away.
Well.. here is it anyway Running SETI@home on an nVidia Fermi GPU

[edit]I know it isn't small thread :) but I still strongly suggest that you read it thoroughly, cuz the guy who started it surely knows what he's doing.[/edit]

---

Who the hell is General Failure and why is he reading my harddisk?¿

One machine (ES-1) keeps hitting the limit in asking for new work, but has only 12 work units. The only other computer I checked is being denied with 15 work units

The limit is 5 per CPU unit & 40 per GPU unit.
AFAIK the 5 per CPU unit means a Dual Core system can have up to 10, a Quad Core up to 20.

---

Grant
Darwin NT

...
[edit]Oh.. and the time calculations on my CPU units are really still WAY off.[/edit]

As your hosts are running stock applications, they're very interesting as examples of the kind of estimate adjustments the servers make. Most active forum members here are running anonymous platform, for which that feature is disabled for now.

The "Number of tasks completed" needs to be at least 10 before BOINC will try to adjust estimates, and for a CPU getting to that point will clearly take longer than most GPUs. That period at the beginning for each host when CPU estimates are unadjusted while GPU tasks have the adjustment is certain to be awkward. If the estimates for your AMD CPU tasks with 7 completed are even worse than those for the Intel CPU tasks with 27 completed, perhaps that's a positive sign. OTOH, the servers are maintaining an overall host average as well as the app version averages, the relative speed of CPU versus GPU tasks on a host may also affect how long it takes for estimates to stabilize as much as they can.

Please keep us posted on future developments, BOINC is trying for a 'one size fits all' method. That usually really means the fit is poor but maybe adequate for all.

                                                               Joe

Okay.. what I am seeing is the AMD estimating at around.. 2:45 per gpu task.. Which falls under not bad. these tend to run between 50 minutes and just under 3 hours. The cpu is not yet crunching SETI as it has been busy on CPDN for some time. Their units last ... 300+ hours.

On the I5 system, I would say the GPU units are pretty close to fair.... Hard to tell due to the mix of units at the moment. But 2 hours is about average.. I have everything throttled back a bit, as I need to use the computers too.

However the CPU units rating themselves at 10 hours on the GT220,(9 to 11:50 that I have seen) is very very far off. These units will take a MAX of about 3
hours to complete, each. 2 at a time.

If someone want to contact me directly to be an "example".. send a message and I will keep them posted directly. As long as it gets to those that can use the information.

---

Janice

...
One machine (ES-1) keeps hitting the limit in asking for new work, but has only 12 work units.
...
Ed

The limit was set at 5 per CPU this time, so your dual core hosts are allowed 10 in progress, single core hosts 5 in progress.

When your hosts finish enough work to get below the limits or the limits are increased, you'll get more work. We have no official word on when the limits may be raised, though I've seen one post suggesting there might have been some change an hour or two ago.

                                                                Joe

Don't bother-DA told me personally he doesn't pay attention to the forums.

I wouldn't expect him to. But I'm sure the various project admins tell him of anything that he needs to be aware of.

Well, we know Jeff reads these boards, or at least the threads he starts, as we saw after last week's outage. AND he acts on our reasonable suggestions. Too bad he had to hide his "new limits" threads due to too much activity, so I can't quote him directly. (8{)

I suspect he is monitoring the server load and upload/download traffic levels, as he did last weekend. I hope he will be able to adjust the cpu/gpu/host limits upward as server load subsides. As Jeff said himself, this is a new protocol, and they (and we) will be adjusting things as they learn what works and what doesn't. As long as the servers remain stable....

The one thing I do NOT expect is lots of changes in a short time period. I think they realized, after the problems a couple weeks ago, that too many changes all at once will really screw up the works, so now they are going to make changes in small steps, watch what happens, then adjust some more. Which is exactly how I would do it.

So relax, stay cool (forecast here is for >100 F through the weekend), and crunch 'em if you got 'em.

Donald
Infernal Optimist / Submariner, retired

...
One machine (ES-1) keeps hitting the limit in asking for new work, but has only 12 work units.
...
Ed

The limit was set at 5 per CPU this time, so your dual core hosts are allowed 10 in progress, single core hosts 5 in progress.

When your hosts finish enough work to get below the limits or the limits are increased, you'll get more work. We have no official word on when the limits may be raised, though I've seen one post suggesting there might have been some change an hour or two ago.

                                                                Joe

Right now I'm processing 76.8 WU's a day on My QX6700 cpu and It's going to take about 6-7 days before I get below this 20 a day WU cap... Then I should be able to get some WU's for the two GTX295 cards, Which can chew through a WU between 2 and 12 minutes a piece(outside of VLARs which GT200 type chips have problems doing, Unlike the 400 series[Fermi]), So these limits are still way too low to My thinking.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

You should be able to get the cufft file here.. http://boinc2.ssl.berkeley.edu/beta/download/cufft32_30_14.dll

Try dropping it in program data/BOINC/projects/setiathome.berkeley.edu Stop BOINC and any clients you have running (SETI, Ect.) restart boinc and it should pick up on it. Check the messages tab and if still trying to download cancel the download.

---

PROUD MEMBER OF Team Starfire World BOINC

my kids are brats my wife doesn't understand me work sucks my boss is an unbearable jerk.


you did say all problems ?

---

That was a good one james (:

---

Thanks for your help. I'll give it a complete read, but it seems dead on. Thanks again to you and perryjay who offered the direct link to the file. Rich

Well....a second rig has run out of Cuda tasks and is not getting any.......
So that is obviously not working right.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Well....a second rig has run out of Cuda tasks and is not getting any.......
So that is obviously not working right.

Check your count of CPU tasks. I had a bunch of VLARs that threw me over the overall limit.

My GPU is now humming away, however I am also wanted for the mass murder of about 80 VLAR WUs.

Gotta run.

---

Join the PACK!

Gawd....term limits in office should work so well as these here.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Well....a second rig has run out of Cuda tasks and is not getting any.......
So that is obviously not working right.

Check your count of CPU tasks. I had a bunch of VLARs that threw me over the overall limit.

My GPU is now humming away, however I am also wanted for the mass murder of about 80 VLAR WUs.

Gotta run.

Yeah, I know......
The freaking point is the GPU was supposed to have a separate limit now.

---

"Time is simply the mechanism that keeps everything from happening all at once."