reducing max_wus_in_progress

I think with the new server updates people are alleowd to get quite a few more workunits than before -- which is part of why the site is running so slow (there are almost 700,000 tasks floating around).



I've dropped the max_wus_in_progress to 3 for both CPUs ans GPUs. Hopefully this will make the site somewhat responsive again.

---

To 3! Holy cow that's drastic since it was 6!

Did I miss the notice? I got 310 completed WUs and still have pages of WUs! What's the max number of units that you get now?

To 3! Holy cow that's drastic since it was 6!

Just trying to get the server working. If things start going smoothly we'll try and increase it and see what happens.

---

959 wu's to report on my main cruncher...

4/8/2011 7:06:09 PM Milkyway@home Sending scheduler request: Requested by user.
4/8/2011 7:06:09 PM Milkyway@home Reporting 1411 completed tasks, requesting new tasks for GPU

and another guy:

4/8/2011 7:11:25 PM Milkyway@home Sending scheduler request: Requested by user.
4/8/2011 7:11:25 PM Milkyway@home Reporting 1137 completed tasks, requesting new tasks for GPU

and another:

4/8/2011 7:11:59 PM Milkyway@home Sending scheduler request: Requested by user.
4/8/2011 7:11:59 PM Milkyway@home Reporting 877 completed tasks, not requesting new tasks


In got more too LMAO

I was scared when i saw 313 wus completed. Now i see why:)

I was scared when i saw 313 wus completed. Now i see why:)

Be nice to be able to report them...that would quickly reduce the DB size.

And yet another (with 2 more outstanding)

4/8/2011 9:08:16 PM Milkyway@home Sending scheduler request: Requested by user.
4/8/2011 9:08:16 PM Milkyway@home Reporting 1430 completed tasks, requesting new tasks for GPU

I wonder how they are going to process all these!!!

I don't know what a "feeder" is other than that it seems to be keeping my machines from reporting...

4/8/2011 9:19:27 PM Milkyway@home update requested by user
4/8/2011 9:19:28 PM Milkyway@home Sending scheduler request: Requested by user.
4/8/2011 9:19:28 PM Milkyway@home Reporting 106 completed tasks, not requesting new tasks
4/8/2011 9:19:36 PM Milkyway@home Scheduler request completed
4/8/2011 9:19:36 PM Milkyway@home Message from server: Server error: feeder not running

---

Please: WCG - Help Cure Muscular Dystrophy

The BOINC feeder is the program that maintains the pool of SQL database connections for the scheduler. It costs plenty of computing resources to set up a connection to an SQL database each time a scheduler request is made, so having this middleman saves these connections for reuse saves this overhead.

The reason the scheduler cannot maintain this is that there really is no one "the scheduler". Each time the scheduler is called, a new scheduler process or thread (I am not sure which) is spawned and then is torn down at the end of the scheduler request.

If the feeder is down, the scheduler cannot work.