Are there server problems as they are difficult to access or very slow to load?

I don't know if Milksop's fast client is helping towards the issues as crunchers run out of work and hammering the servers?

All my rigs are crunching MW fine and D/Ling work. But, the U/Ling of results and "waiting to report" seems to be particularly slow.

DI cannot see it in the Server Status, but do any of the servers need kicking?

I think it is simply the effect of the fast client -- it pushes results and requests new work at something like 50 times the previous rate. Sort of a jailbreak effect on the servers. I think the problems will persist until folks at the project can release new larger (and slower) workunits to reduce the load on the server. It is one of the unintended but predictable effects of having the optimixed client available to all who wish to use it.

Are there server problems as they are difficult to access or very slow to load?

I don't know if Milksop's fast client is helping towards the issues as crunchers run out of work and hammering the servers?

All my rigs are crunching MW fine and D/Ling work. But, the U/Ling of results and "waiting to report" seems to be particularly slow.

DI cannot see it in the Server Status, but do any of the servers need kicking?

---

There were some quite serious corruptions of the "profile" table in the database. I have fixed them and now everything should be back to normal (including editing of profiles and user of the day).

---

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

I've gotten all kinds of errors today, but at the moment I'm getting

01/11/2008 17:54:40|Milkyway@home|Sending scheduler request: Requested by user. Requesting 876 seconds of work, reporting 0 completed tasks
01/11/2008 17:54:45|Milkyway@home|Scheduler request completed: got 0 new tasks
01/11/2008 17:54:45|Milkyway@home|Message from server: Server error: can't attach shared memory

Also, the feeder and like half of the other stuff is offline?

I've gotten all kinds of errors today, but at the moment I'm getting

01/11/2008 17:54:40|Milkyway@home|Sending scheduler request: Requested by user. Requesting 876 seconds of work, reporting 0 completed tasks
01/11/2008 17:54:45|Milkyway@home|Scheduler request completed: got 0 new tasks
01/11/2008 17:54:45|Milkyway@home|Message from server: Server error: can't attach shared memory

Also, the feeder and like half of the other stuff is offline?

Same problem here.

Yup. They are back on as of 5 seconds ago.

---

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

(including editing of profiles ...).

Yeah, it works now! Thanx Dave! :-)

---

Member of BOINC@Heidelberg and ATA!

My BOINCstats

Dave

Thanks for coming in on a Saturday and give the servers a tickle and kick where appropriate.

I assume the Server status notice of zero WU available to send (when these servers/assimilators/etc are back online) is due to those of us using Milksop's fast client. This will suck down WUs at a tremendous rate.

Can the creation of new WUs be made faster?

As you say, the servers are working again and I have sent the WU results "ready to report". Now just waiting for some new WUs to crunch. Just need to streamline this with the other project I am now crunching as well.

Yes, the optimized client is crunching units faster than we can churn them out. This might be a bottleneck and a downside to the optimized client. You folks have to battle for new workunits. However, I'll see what we can do, if anything, about this problem.

---

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

I wouldn't be too concerned at this stage. If the work is getting completed in 2% of the time it use to take, then I think we can wait for some work if necessary!

Hopefully more science is being done for the benefit of the project!

I wouldn't be too concerned at this stage. If the work is getting completed in 2% of the time it use to take, then I think we can wait for some work if necessary!

Hopefully more science is being done for the benefit of the project!

Agreed

The now spare cycles are available to other distributed projects

indeed, and even though the word generator can't keep up we're still doing way way way more crunching than we used to :)

I haven't got a workunit or seen work available for hours now. Is that just me or has the workgenerator crashed?

I haven't got a workunit or seen work available for hours now. Is that just me or has the workgenerator crashed?

I think with the fast apps we've crunched the current WU queue empty. ;-)

---

Lovely greetings, Cori

I haven't got a workunit or seen work available for hours now. Is that just me or has the workgenerator crashed?

I think with the fast apps we've crunched the current WU queue empty. ;-)

That is my impression as well.

The fast client just sucks down the queue available and the Feeder just cannot keep up.

I think those with the old client, and a cache, are still crunching. But this will not last as there is no WUs to send even to them.

But since new WUs are created from results crunched before we may expect many WUs in the near future again (I hope). ;-)

---

Lovely greetings, Cori

As fast as they are created they are taken up by someone. I think it is now a matter of requesting more work at the right time to get more units.

---

Never surrender and never give up. In the darkest hour there is always hope.

But since new WUs are created from results crunched before we may expect many WUs in the near future again (I hope). ;-)

That is certainly a point worth considering.

The more we crunch now, with long gaps, the more we may have to crunch soon. But, it still comes down to the capacity of the feeder, which is set up for the outputs before the fast client came out yesterday.

It should be remembered that the Admins are tweaking a new client, which is based on a similar code to the Milksop client release. So, in the light of this per-new MW fast client release, they may need to consider what they want to study and how quickly.

There is discussion around that in other threads.

It should be remembered that the Admins are tweaking a new client, which is based on a similar code to the Milksop client release. So, in the light of this per-new MW fast client release, they may need to consider what they want to study and how quickly.

I do remember a mention about doing a larger portion than is being done currently, so that should make the wu's longer again. (not sure if it will happen or not)

---

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

I don't think many will appear untill the next group is added. The total has gone from 36000 to 17700 wu's.