Had 2 CUDA/CAL hosts, turned off, cause of the heat today, 36C and still 30C. atm., it's crazy lazy weather.
And got, after UPLoading a few hundred tasks, a bunch of new tasks, MB WU's, excellent for this host, a QX9650(@3.4G;1450MHz FSB;1x9800GTX+ and 1 GTS250.
Running Windows XP64, BOINC 6.10.56 (x64) and Optimized CPU (SSSE3x) and GPU app.
And use REScheduler, so I won't send back a REJected/killed, VLAR!
Use the [i]automatic mode, depending of the amount of work, between 3 and 6 hours. No RESents of killed VLARS, since it's a waiste and why NOT crunch them, as well, as I was astonished, how much tis happens.
Including myself, no problems, only when you have > 250 - 400 WU's, you should check, Connecting to Local Host, or password incorrect(?).
Hope I get some ASTRO PULSE tasks. (Take 2.5 -6 hours)

---

Hm, outgoing traffic drops considerably and we have only half week to fill caches and even before after small outage it took much more hours on maxed bandwidth to low work demand... that is, very likely that almost all fast enough hosts are underloaded now and will not refill caches due to remaining time before next outage... I have big doubts in usefulness of such work restriction now.

You can tell that alright

I have 0 cache.. Only have exact amount in cache as those i crunch for the moment.

It won't simply fill up at all..

Regards Vyper

---

_________________________________________________________________________
Addicted to SETI crunching!
Founder of GPU Users Group

I have big doubts in usefulness of such work restriction now.

In the Tech News Matt posted about several software updates they did. Wouldn't surprise me if this present restriction is an unintended result of that.
There have been times in the past were updates & patches have clobbered existing tweaks & settings.

---

Grant
Darwin NT

This is brilliant!

Normally after a significant outage I can't upload my results and therefore can't download any new tasks. However this time that's not the case. Uploads were no problem after the outage and a few new tasks (number is 20) were downloaded to the hosts that had run dry.

I can hope that this is the intended behavior and more WUs will flow freely as the network/server traffic after the outage eases.

---

This is brilliant!

Normally after a significant outage I can't upload my results and therefore can't download any new tasks. However this time that's not the case. Uploads were no problem after the outage and a few new tasks (number is 20) were downloaded to the hosts that had run dry.

I can hope that this is the intended behavior and more WUs will flow freely as the network/server traffic after the outage eases.

The problen that it eased already, look graph. But limit still here so currently outgoing bandwidth heavely underused (and we will have it only half of prev time).

Sadly, While my CPU queue remains chock full of Astropulse and multibeam VLAR goodness, the New NinjaB@5t!Red is stone cold idle. Oh well.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

It may be just to give it some time for the servers to process all the uploads we sent in this morning. I notice though the pendings are dropping fairly quick I still have a lot that have been finished by both me and my wingman that are still waiting validation. I hope that once they get caught up they will open the floodgates again.

---

PROUD MEMBER OF Team Starfire World BOINC

This is brilliant!

Normally after a significant outage I can't upload my results and therefore can't download any new tasks. However this time that's not the case. Uploads were no problem after the outage and a few new tasks (number is 20) were downloaded to the hosts that had run dry.

I doubt the new limit has had any bearing on you being able to upload all your results & download new work as the servers were being hammered as hard as they ever have been even with the limitation in place. It is most likely a result of the upgrades they did while the system was down.

---

Grant
Darwin NT

This is brilliant!

Normally after a significant outage I can't upload my results and therefore can't download any new tasks. However this time that's not the case. Uploads were no problem after the outage and a few new tasks (number is 20) were downloaded to the hosts that had run dry.

I doubt the new limit has had any bearing on you being able to upload all your results & download new work as the servers were being hammered as hard as they ever have been even with the limitation in place. It is most likely a result of the upgrades they did while the system was down.

But if the downloads/outstanding WUs are limited to 20 tasks per host after the outage, the download pipe won't stay clogged for 24+ hours, thus blocking uploads as in the past. Bottom line... my host has work shortly after the servers came back online. In the past it might take a full day before my results could be fully uploaded and requests for new work issued.

Again... This is brilliant!!!

---

But if the downloads/outstanding WUs are limited to 20 tasks per host after the outage, the download pipe won't stay clogged for 24+ hours, thus blocking uploads as in the past.

I agree, but what i'm saying is that all those uploads went through early on- when the download pipe was as full as it's ever been. Not only that, but the uploads went through at almost the highest rate ever- while downloads were still going flat out.
Which would indicate that the reduced upload bottleneck wasn't as a result of the limit on tasks in progress, but more likely upgrades/ patches done while the system was down. Or the empty queues from the system being down.

---

Grant
Darwin NT

This is brilliant!

Normally after a significant outage I can't upload my results and therefore can't download any new tasks. However this time that's not the case. Uploads were no problem after the outage and a few new tasks (number is 20) were downloaded to the hosts that had run dry.

I doubt the new limit has had any bearing on you being able to upload all your results & download new work as the servers were being hammered as hard as they ever have been even with the limitation in place. It is most likely a result of the upgrades they did while the system was down.

But if the downloads/outstanding WUs are limited to 20 tasks per host after the outage, the download pipe won't stay clogged for 24+ hours, thus blocking uploads as in the past. Bottom line... my host has work shortly after the servers came back online. In the past it might take a full day before my results could be fully uploaded and requests for new work issued.

Again... This is brilliant!!!

I have 4 gpus here and I have no work for them, Brilliant? Sounds stupid to Me, As in Your not wanted, Go away...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Hmm, just got 15 Work Units to crunch, however the To Completion times are way, way, way too long. This is the first time it's requested work since they implemented the changes of a couple of weeks ago- as that resulted in estimated To Completion times that were way, way, way to short & my 4 day caches ended up with 10 days worth.
I take it those chages have been reversed, or the updates have undone them?



EDIT
Just edited my DCF to see what would happen. Prior to the previous server changes it was around .1 most of the time, found it was around .95.
Changed it to .1 again & downloaded & whole bunch of work, several times, till i got the "This computer has reached a limit on tasks in progress" message again. I probably got about 30 or so Work Units before the message came up again. Enough to keep me going for 1.5, maybe 2 days, but not enough to fill my 4 day cache.

---

Grant
Darwin NT

Like I already mentioned in one of the other threads..

MilkyWay@home have a limit of 12 tasks in progress.
If BOINC ask for more, BOINC get:

Message from server: No work sent
Message from server: (reached limit of 12 tasks in progress)

Because of the SETI@home server say not the max limit, I guess something is wrong here.

I believe the Milkyway Limit is 6 Tasks per Core

Got 11 WUs 15 minutes ago to go with the remaining 50 of the 78 given before the outage. So I'm Fine for the Time Being.

The SETI app Data says
http://setiathome.berkeley.edu/host_app_versions.php?hostid=5178843

My Guess is this new limit Includes everything (In Progress/Valid/Pending/Errored) hopefully I'll be able to get a few more when all this gets written to the database.

Has anyone here generated any -12 errors? I have, 6 in the last 7 days... Out of thousands of good results...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I only had one -12 error during the outage. Turned in this morning.

---

PROUD MEMBER OF Team Starfire World BOINC

Has anyone here generated any -12 errors? I have, 6 in the last 7 days... Out of thousands of good results...

I have 2 errors with an exit status of 1. One was from the CPU, and one was from the GPU. Some of my wingmen timed out, but that was bound to happen.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

Unfortunatly some of us have hosts that will process more than 20 WU's at a time. Case in point is a dual Intel X5680 system that I have with 2 Fermi cards running two instances per card. That is a total of 28 tasks at a time that could be processed if this limitation was lifted. Also I am building a system with a Quad sockets and each cpu has 8 cores and hyperthreading - and two fermi cards to boot. That will be 68 tasks at a time processing.

If this behavior is temporary and expected that is fine but if this is the way it is going to be I am seriously considering other options for my resources. This system is being built as a mega-cruncher and has a significant price tag associated with it. If it cant be used to its full potential I won't bother.

I'm not saying I'm dumping S@H or anything like that but do want to make it known that there are individuals with systems that are more than able to process more than 20 WU's at a time and a higher limit should be implemented.

Todd

---

Has anyone here generated any -12 errors? I have, 6 in the last 7 days... Out of thousands of good results...

I've had no errors at all.

---

Grant
Darwin NT

Network traffic has dropped right off & there is plenty of work ready to send, so i guess almost everyone has finally hit the task limit.

Good, maybe they'll lift the limit so we can build a cache.