Duration of unsent results is growing?

josep
josep
Joined: 9 Mar 05
Posts: 63
Credit: 1,156,542
RAC: 0
Topic 189805

Just to be curious:

I have 8 finished and reported WUs now, still unsent to other machines, so they are pending for validation. Some of the WUs are 5 days old for me.

My results page is here:

http://einsteinathome.org/host/70907/tasks

I have read in older posts that the scheduler normally waits 3 days to find a machine with the same data file, and after that, it tries to send the WU to a fast machine.

Has this delay time been changed now? In the "Server Status" web page the "oldest unsent result" is more than 6 days old...

josep
josep
Joined: 9 Mar 05
Posts: 63
Credit: 1,156,542
RAC: 0

Duration of unsent results is growing?

Well, I see now that I am not the only one. There is another recent thread in "Problems and bug reports" forum about this question. Several users say they have now lots of "lonely WUs", that no one else is crunching.

You can see the thread here

Divide Overflow
Divide Overflow
Joined: 9 Feb 05
Posts: 91
Credit: 183,220
RAC: 0

This is one side effect of

This is one side effect of the localization of work files for this project.
Your system doesn't download individual WU's. From time to time it downloads a rather large file which contains a "chunk" of work it can draw off of. This same file is sent out to several other computers, and until the work is exhausted, you'll draw off of it untill it is finished. You'll find you're crunching with a lot of the same people over and over for a while because they all have the same localized work file. You'll also notice that when you need new work it happens very quickly since the file is already on your hard disk. :) When the work file is exhausted, you'll be sent a new one and be crunching with a different group of folks out there.

When several of the other people who have been assigned the same localized work file as the one you are working off of don't crunch very fast, the work doesn't get "sent out" to them, and you'll have the condition you're experiencing now. Eventually there will be a time-out point where that localized work file is sent out to another host asking for work and you'll get some new people assigned to your WU.

Hope this helps! (And I hope I got most of this correct!)

josep
josep
Joined: 9 Mar 05
Posts: 63
Credit: 1,156,542
RAC: 0

Thank you David, I will wait

Thank you David, I will wait for them be sent to other crunchers, no problem.

The "time-out point" you mention used to be about 3 days, as I have seen in other threads. But now it seems to be larger, possibly acording to the extended deadlines we have now.

Certainly, my oldest crunched WUs are now being sent to other crunchers, so the oldest unsent WU does not surpass 5 or 6 days old.

Thanks again (and excuse my poor English speaking)


Bruce Allen
Bruce Allen
Moderator
Joined: 15 Oct 04
Posts: 1,109
Credit: 172,125,663
RAC: 0

I've changed the cut-off time

I've changed the cut-off time back from 7 days to 3.5 days. Unsent work older than this gets sent out with rather high priority. It may take a day or two for the scheduler to catch up with this change.

Bruce

Director, Einstein@Home

Ross Morgan
Ross Morgan
Joined: 20 Feb 05
Posts: 18
Credit: 122,639
RAC: 0

RE: I've changed the

Message 16077 in response to message 16076

Quote:

I've changed the cut-off time back from 7 days to 3.5 days. Unsent work older than this gets sent out with rather high priority. It may take a day or two for the scheduler to catch up with this change.

Bruce

Yes i noticed that. I have now WU's from a couple of different data files and on some of them the WU has been sent out to other crunchers days before i get them.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.