Am I the only one that has not been getting the full 10 days of tasks when you set it to keep 10 days of tasks in queue? I keep getting:

10/16/2010 10:51:43 PM SETI@home Requesting new tasks for CPU and GPU
10/16/2010 10:51:52 PM SETI@home Scheduler request completed: got 0 new tasks
10/16/2010 10:51:52 PM SETI@home Message from server: No work sent
10/16/2010 10:51:52 PM SETI@home Message from server: This computer has reached a limit on tasks in progress

Which this is only 2 days of GPU tasks (634) and probably 4-5 days of CPU tasks (424). It just makes me wonder why you would be allowed to set it to 10 days if you can't get 10 days of tasks. I have verified account settings and computer settings to make sure I am not missing something.

TIA for any thoughts/tips

---

Until the bandwidth usage dies down some, the host limits are in place. Those limits are 40 per CPU core, and 320 per GPU. This is to ensure everyone has a chance to at least get some work. Usually on Sunday/Monday, the limits are removed and we will be able to load up before the Tuesday outage.

---

I sure hope I can get at least another 3 days of GPU tasks for this system to keep running during the outage in that small amount of time. I am sure there are others that hate seeing their systems sit idle for 1/2 of the scheduled downtime or more.

---

Evening

And I am not in a good humor.

Does anyone know how stupid this is?

I still have to wonder why people incorrectly set a ten day cache when they did not know that it would double, triple or quaddruple the stress on the Servers. We all know that the servers have issues and when you increase the stress it is going to cause problems. During the last outage you could see that 3.5+ megabits/sec were the 230000+ computers attempting to contact the scheduler. That is rougly 4% of the 100 megabit bandwidth upstream. When uploads start to happen you can see go over 40 megabits/sec on the network link. When downloads are enabled that trashes uploads and scheuler requests. It is all those 10 day caches pushing out other Seti Users.

So when the BAD Advice happened, too many people listened to the BAD Advice! You also should know by now that there are limits on the number of Workunits that you can download right now. That is limited to not overrun the bandwidth available.

So as I have cut back on Seti, so the greedy can get their fill (listening to bad advice)... I feel no sympathy for you. I will not be the straw that broke the camels back... So on the next Crash, please start a Thread I was the Seti User that broke the Camels Back! Then you can brag about how large your cache size is. Then complain that you can not get work or that you still have work and expect others to praise you or feel sorry for you.

Regards

---

Please consider a Donation to the Seti Project.

I think it's pretty uncouth to call your fellow crunchers stupid.

Someone came here asking an honest question, and you have to foist the project's problems on him.

---

Evening

And I am not in a good humor.

Does anyone know how stupid this is?

I still have to wonder why people incorrectly set a ten day cache when they did not know that it would double, triple or quaddruple the stress on the Servers. We all know that the servers have issues and when you increase the stress it is going to cause problems. During the last outage you could see that 3.5+ megabits/sec were the 230000+ computers attempting to contact the scheduler. That is rougly 4% of the 100 megabit bandwidth upstream. When uploads start to happen you can see go over 40 megabits/sec on the network link. When downloads are enabled that trashes uploads and scheuler requests. It is all those 10 day caches pushing out other Seti Users.

So when the BAD Advice happened, too many people listened to the BAD Advice! You also should know by now that there are limits on the number of Workunits that you can download right now. That is limited to not overrun the bandwidth available.

So as I have cut back on Seti, so the greedy can get their fill (listening to bad advice)... I feel no sympathy for you. I will not be the straw that broke the camels back... So on the next Crash, please start a Thread I was the Seti User that broke the Camels Back! Then you can brag about how large your cache size is. Then complain that you can not get work or that you still have work and expect others to praise you or feel sorry for you.

Regards

During the last outage limits were set at 40 per cpu and 320 per gpu so even at my 4 day setting I did not fill up. So the cache setting had nothing to do with bandwith.

---

Easy, folks.

Let's not let the frustrations of the day cause us to start infighting amongst ourselves.
We are all on the same team.

Meow meow.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Post #2 by Blake Bonkofsky answered the OP's question and no further comments were necessary.

---

Boinc....Boinc....Boinc....Boinc....

Until the bandwidth usage dies down some, the host limits are in place. Those limits are 40 per CPU core, and 320 per GPU. This is to ensure everyone has a chance to at least get some work. Usually on Sunday/Monday, the limits are removed and we will be able to load up before the Tuesday outage.

And where/when it is stated that these particular limits are in place?
With my 6.6.20 client, they are: 0 per CPU and ∞ for GPU (so far). For the past few weeks, even when I run dry with CPU tasks, I always bump into limit wall, while cuda wu's keep pouring in like there's no tomorrow. I tried with staying below 100 GPU wu's, I even recapture and crunch trough all of my ghosts but to no avail. Only time frame for getting tasks for my quad is the first hour after the opening of flood gates and it usually gets 20-25. Until the next server run, my only option is to reschedule cuda wu's.

Any suggestions?

---

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

Is your client requesting CPU work and not getting it? Or is it not requesting CPU work at all?

---

Until the bandwidth usage dies down some, the host limits are in place. Those limits are 40 per CPU core, and 320 per GPU. This is to ensure everyone has a chance to at least get some work. Usually on Sunday/Monday, the limits are removed and we will be able to load up before the Tuesday outage.

And where/when it is stated that these particular limits are in place?
With my 6.6.20 client, they are: 0 per CPU and ∞ for GPU (so far). For the past few weeks, even when I run dry with CPU tasks, I always bump into limit wall, while cuda wu's keep pouring in like there's no tomorrow. I tried with staying below 100 GPU wu's, I even recapture and crunch trough all of my ghosts but to no avail. Only time frame for getting tasks for my quad is the first hour after the opening of flood gates and it usually gets 20-25. Until the next server run, my only option is to reschedule cuda wu's.

Any suggestions?

Have you double checked your local preferences?

Cheers.

---

It sure asks for work... Lots of work :-) (4.5 days to be exact)

17-Oct-10 12:06:58	SETI@home	Reporting 1 completed tasks, requesting new tasks
17-Oct-10 12:06:58	SETI@home	[sched_op_debug] CPU work request: 1254340.58 seconds; 0 idle CPUs
17-Oct-10 12:06:58	SETI@home	[sched_op_debug] CUDA work request: 0.00 seconds; 0 idle GPUs
17-Oct-10 12:07:54	SETI@home	Scheduler request completed: got 0 new tasks
17-Oct-10 12:07:54	SETI@home	[sched_op_debug] Server version 611
17-Oct-10 12:07:54	SETI@home	Message from server: No work sent
17-Oct-10 12:07:54	SETI@home	Message from server: This computer has reached a limit on tasks in progress

Local prefs are fine too. In fact, everything is fine when there are no limits or when they are very high. i.e.Sept.3-6 320/CPU 2560/GPU. Any other limit prevents my CPU from getting work 1 hour after server run starts. Maybe it has something to do with my choice of apps? Normaly I use CPUs for Astropulse and GPU for cuda, but within 24hrs when I crunch my last AP, I'll have to add AKv8b to app_info and start reschedule work for my quad. And I've been doing this since the problem with their AC unit emerged.

[edit]CUDA Fetch? No problem, just say how many do you need![/edit]

17-Oct-10 12:26:56	SETI@home	Reporting 1 completed tasks, requesting new tasks
17-Oct-10 12:26:56	SETI@home	[sched_op_debug] CPU work request: 1262277.22 seconds; 0 idle CPUs
17-Oct-10 12:26:56	SETI@home	[sched_op_debug] CUDA work request: 3695.48 seconds; 0 idle GPUs
17-Oct-10 12:27:47	SETI@home	Scheduler request completed: got 7 new tasks
17-Oct-10 12:27:47	SETI@home	[sched_op_debug] estimated total CPU job duration: 0 seconds
17-Oct-10 12:27:47	SETI@home	[sched_op_debug] estimated total CUDA job duration: 2481 seconds

---

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

I don't run AstroPulse, so I can't comment, but I know I have had NO problems getting MB work. Why not just run both?

---

It sure asks for work... Lots of work :-) (4.5 days to be exact)

17-Oct-10 12:06:58	SETI@home	Reporting 1 completed tasks, requesting new tasks
17-Oct-10 12:06:58	SETI@home	[sched_op_debug] CPU work request: 1254340.58 seconds; 0 idle CPUs
17-Oct-10 12:06:58	SETI@home	[sched_op_debug] CUDA work request: 0.00 seconds; 0 idle GPUs
17-Oct-10 12:07:54	SETI@home	Scheduler request completed: got 0 new tasks
17-Oct-10 12:07:54	SETI@home	[sched_op_debug] Server version 611
17-Oct-10 12:07:54	SETI@home	Message from server: No work sent
17-Oct-10 12:07:54	SETI@home	Message from server: This computer has reached a limit on tasks in progress

Local prefs are fine too. In fact, everything is fine when there are no limits or when they are very high. i.e.Sept.3-6 320/CPU 2560/GPU. Any other limit prevents my CPU from getting work 1 hour after server run starts. Maybe it has something to do with my choice of apps? Normaly I use CPUs for Astropulse and GPU for cuda, but within 24hrs when I crunch my last AP, I'll have to add AKv8b to app_info and start reschedule work for my quad. And I've been doing this since the problem with their AC unit emerged.

[edit]CUDA Fetch? No problem, just say how many do you need![/edit]

17-Oct-10 12:26:56	SETI@home	Reporting 1 completed tasks, requesting new tasks
17-Oct-10 12:26:56	SETI@home	[sched_op_debug] CPU work request: 1262277.22 seconds; 0 idle CPUs
17-Oct-10 12:26:56	SETI@home	[sched_op_debug] CUDA work request: 3695.48 seconds; 0 idle GPUs
17-Oct-10 12:27:47	SETI@home	Scheduler request completed: got 7 new tasks
17-Oct-10 12:27:47	SETI@home	[sched_op_debug] estimated total CPU job duration: 0 seconds
17-Oct-10 12:27:47	SETI@home	[sched_op_debug] estimated total CUDA job duration: 2481 seconds

Well AP's are usually few and far between but I also noticed that your versions of BOINC are also old so why not try upgrading it to 6.10.XX to see if that helps.

Cheers.

---

I reached my Quota and have run out of work twice today. The quotas are way too low.
EDIT: I bet the graphs are peaked, why wouldn't they be with every computer asking for more work, over and over again. The quotas cause a backup just like a slow jerk in the left lane!

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Until the bandwidth usage dies down some, the host limits are in place. Those limits are 40 per CPU core, and 320 per GPU. This is to ensure everyone has a chance to at least get some work. Usually on Sunday/Monday, the limits are removed and we will be able to load up before the Tuesday outage.

Have you actually seen these numbers? I have filled my cache and have 157 CPU and 133 GPU and have 3 GPU's
10/17/2010 4:42:11 AM | SETI@home | Message from SETI@home: This computer has reached a limit on tasks in progress

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I just rescheduled everything to GPU, see if it gets more than the 5 trying to report.

EDIT: The only reason I noticed was because like yesterday morning I woke up cold...Had to get up and clear downloads as my computer is my room heater.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Well all 3 of my pc's have enough CPU/CUDA work for about 5 days now on the limits currently set, all of them on BOINC 6.10.56 with Lunatics 0.36 installer.

Cheers.

---

Well all 3 of my pc's have enough CPU/CUDA work for about 5 days now on the limits currently set, all of them on BOINC 6.10.56 with Lunatics 0.36 installer.

Cheers.

Maybe I should ditch the new client and stay with the old....

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Looking at the top hosts page maybe the older clients are getting thru this mess better than the newer one....

---

Official Abuser of Boinc Buttons...
And no good credit hound!