To the Project Admins - it's now 0.15am UTC Friday

As a loyal cruncher who has been out of work since about 3.00pm UTC this afternoon.

I would be gratified if one of the small number of MW Project Admins could look in to this thread.

We would appreciate a comment on what is the current position?

- what is happening?
- the Server Status shows no new work and the Results in Progress running down?

Can we expect new work to crunch soon?

2nd!

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Note, I believe these folks are back east -- so it is already end of the day there -- perhaps we will not see a reply or some corrective effort until tomorrow.... The lack of available work started this morning (back east).

---

We work around the clock. We used to generate work automatically. However, we are generating different WU's now that are longer so the optimized clients won't return the work so fast and therefore our assimilator can catch it's breath.

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

We work around the clock. We used to generate work automatically. However, we are generating different WU's now that are longer so the optimized clients won't return the work so fast and therefore our assimilator can catch it's breath.

Well DAMMIT Dave!!
Thanks for the info! HeHeHe!

---

A clear conscience is usually the sign of a bad memory

We work around the clock. We used to generate work automatically. However, we are generating different WU's now that are longer so the optimized clients won't return the work so fast and therefore our assimilator can catch it's breath.

Fine, fine! :-)))

---

Lovely greetings, Cori

This sounds good. If it takes load off the servers, it's definitely worth waiting for (my MW WUs are almost gone, but I have three other projects to take over, so it's not as if the CPU cycles are wasted).

Excellent -- by the way, is this a case of working on getting new work units out --- (as in sometime in a day or so)? I ask as I've (we've) not seen any new work for the day.

We work around the clock. We used to generate work automatically. However, we are generating different WU's now that are longer so the optimized clients won't return the work so fast and therefore our assimilator can catch it's breath.

---

We work around the clock. We used to generate work automatically. However, we are generating different WU's now that are longer so the optimized clients won't return the work so fast and therefore our assimilator can catch it's breath.

Hmm...what # do these go by? The server still states 0 wu's.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

OK - looks like some work is getting created -- doesn't *appear* to be longer processing though.

Excellent -- by the way, is this a case of working on getting new work units out --- (as in sometime in a day or so)? I ask as I've (we've) not seen any new work for the day.

We work around the clock. We used to generate work automatically. However, we are generating different WU's now that are longer so the optimized clients won't return the work so fast and therefore our assimilator can catch it's breath.

---

Hmm...what # do these go by? The server still states 0 wu's.

I believe these could be #gs_625_? Run time avg. the same for me.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Agree regarding run times -- gs_626 and gs_627

I believe these could be #gs_625_? Run time avg. the same for me.

---

Thanks Dave for the reply and the flood of work, now being crunched vigorously (If later than everyone else).

Also, like others have commented - WU run times seem to be similar or the same as before.

Same here, just over seven minutes on my box, which is totally average.

Well yes, we've been manually creating them for about a month now that way. We've been prepping for the release of the faster client so we made that change a while ago. I usually am able to keep the turnaround to about < 6 hours when workunits run out. At least that's my goal

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

Looks like the new work created lasted about 6 hours, before returning to parched conditions.

Looking at some of my rigs, they appear to have stopped crunching approximately between 6.00 am (UTC) and 07.30 am) this morning.

Looking forwards to another lot of new work?

Mine are all gone and the box is not getting any new ones.

The work is coming through well ATM, but history shows things dry up when all seems to be running smoothly

I am I a cynic, or what?

Still spotty for me. I will get 0-3 for awhile, and then get 20.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Looks like we are entering a desert now, as the work is drying up.

Now to bring other projects on board overnight.

Can we use today (Friday 14th November) to get things running smoothly for the week end?