What I was trying to suggest is that Reporting is the act of telling the scheduling server that a task has been completed and uploaded to the upload server. True?

---

I've been babysitting the farm all day. As long as a couple get uploaded, I can then do an update to report 100 tasks. Then I can get more work.

I was babysitting it all day too. But I can only report them at the rate that they upload. Which is slower than the rate at which they are computed. So the pending cache just grew and grew and never let up

Yep uploads remain borked.

---

I've been babysitting the farm all day. As long as a couple get uploaded, I can then do an update to report 100 tasks. Then I can get more work.

Thank you for the hint. I tried a manual update and suddenly it started uploading......
--edit----------
Rats, it looks like it stalled again...
--edit---
Tried the 8 uploads trick. And that got something moving again. I even got some Seti downloads. Then it started timing out again so I dropped it back to 2. And it is still clumping along uploading.
--edit---
Apparently leaving it at 8 uploads/downloads keeps enough connections "active" that 1 or 2 get through every once in a while.

Tom

---

A proud member of the OFA (Old Farts Association).

This is getting tiring ...
I up'd my transfer count to 16 which seems to have helped by having more connections open.

---

Why stop at 8? I put mine at 14 simultaneously long ago, and it has helped me through many of these bottlenecks. It's not 100% successful, but enough get through that I can usually get enough downloads to keep reasonably busy. Also, if your machines process units super fast, and you are completely unable to get new work because of too many downloads, you might try setting "No new tasks" and nurse all the uploads through. When they are all uploaded, you can turn new work back on and, hopefully, fill your caches completely, or nearly completely, all at once, before too many new units complete and build up the backlog, resulting in the old, frustrating message, "Not requesting tasks: too many uploads in progress" bites your machines from behind, so to speak.

Just a thought, eh?

Yes, Brent, you've got the right idea! (I was typing my response to Tom when you posted, so I didn't see it. ) I think I will boost mine from 14 1o 16, also. I made a bold move to 14 years ago, long before GPU processing took SETI to its "Next Generation". I guess it's time to add a couple more to mine, too. :-)

I usually keep my transfers set to 4 and try to keep my connection times staggered.
With a 5mb connection and 3 fast computers filling the pipe, it still allows web pages to load without a noticeable difference since most pages open 30+ connections on their own.

With transfers set at 16, my pages just crawl ...

---

Multiple retries managed to clear my backlogs. Most went without to much trouble but there is always WU or 2 that just doesn't want to go.

Edit-
Or maybe I was just very lucky to try clearing the backlog at that point in time, as since then uploads have become even more reluctant to go through.

---

Grant
Darwin NT

Lucky....
As soon as I get one backlog cleared one of the others decides to grow a backlog, so I've given up trying and just let it happen. Anyway it's only a few hours to the outrage - anyone taking odds on it being a big one this time?

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Yes, Brent, I completely understand. I still remember back in the first half of the last decade of the 20th century (really sounds old, that way, eh!), when I upgraded to the new "state of the art" 14K telephone modem. It was so much faster than my previous modem that I fell in love with it at once! A few years ago I was very lucky to be able to subscribe to a 150 Mbps service, which actually provides around 160-170 Mbps, and occasionally even 180 Mbps. It's been heaven, and I know how lucky I am. However, if that giant, greedy, corporate US provider keeps raising their rates, I may have to start downgrading their service. :-(

This is getting tiring ...
I up'd my transfer count to 16 which seems to have helped by having more connections open.

. . Bl(*dy tedious I would say. I'm ready to turn it all off, what's the point when you can't get work. I can't babysit 4 machines 24/7.

Stephen

:(

Rob, that is where BoincTasks shines! The ability to view/control all computers on one screen.

I actually have two BoincTasks going right now on different computers. One with the Transfers screen, one with the Projects screen.
Retry the transfer first, then update the projects on the other.

LOL it works :D

---

Hi Stephen. When I simply can't get enough work from SETI to keep my machines active, I change my local preferences cache to store 0.05 days of work and 0 additional days of work, then switch Einstein from "No new tasks" to "Allow new tasks". That takes the pressure off. I check back periodically. When SETI units become available again, I just turn off new tasks for Einstein, then reset my cache to what I usually have. With the cache set to 0.05 days, I don't have the annoying, well-known problem of Einstein taking over the machines with a huge download of units with very short deadlines. Within an hour or so I'm back to pure SETI again.

It's just a thought that might help, if it works for your situation and personal preferences. :-)

Have to agree. BT has let me babysit the farm while I piddle around with other things on the daily driver, like bookkeeping, reading email and forum posts and watching my favorite YT tech channels. Occasionally flip over to the BT windows and hit update on the crunchers and go back to what I was doing elsewhere.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Hi Stephen. When I simply can't get enough work from SETI to keep my machines active, I change my local preferences cache to store 0.05 days of work and 0 additional days of work, then switch Einstein from "No new tasks" to "Allow new tasks".

You can do this without any manual intervention of changing settings back and forth... in the Project Preferences in your backup project's profile, set the Resource Share to "0" zero. BOINC will then only download a minimal amount of work to keep your CPU/GPU busy without keeping a cache, only when your primary project with a non-zero Resource Share cannot do so. You can then keep Allow New Tasks for the backup all the time so your computers don't sit idle pending intervention if the primary project is short of work or down.

---

This is getting tiring ...
I up'd my transfer count to 16 which seems to have helped by having more connections open.

Hi All, where and how do I increase the transfer count?

---

Hi All, where and how do I increase the transfer count?

As always, Client configuration

In your cc_config
<max_file_xfers>16</max_file_xfers>
<max_file_xfers_per_project>16</max_file_xfers_per_project>

---

Thank you, Richard! I don't like having to muck around in there, but that helped. :)

---