I've noticed that EInstein downloads a new wu very close to the end of the previous one. When it does this, it generates a scheduling event - "files downloaded".
If you have Einstein set to a very low CPU quota, what frequently seems to happen on my machine is it gets pre-empted with 2-3 minutes left to run, finally get's it's time slice, but then in those last feq minutes, calls for more work and basically shoots itself before it can finish the wu.
I end up with a new wu, and the original, now with perhaps just 1 minute left to run.
Why does Einstein wait so late into the wu before requesting work?
Copyright © 2024 Einstein@Home. All rights reserved.
"Just in time "downloading.
)
Go to your account, general preferences, network usage,and set a greater value for it. I use 0.05 days.
Tullio
The timing of the download is
)
The timing of the download is a function of BOINC, not the project itself. If the project has dipped below its share of the queue ("Connect every X"), BOINC will go and ask for work for that project.
Example:
Queue 10 hours.
Project A share 90
Project B share 10
When Project A dips below 9 hours of wall time remaining, it is time to ask for more work from A. If Project B dips below 1 hour of wall time remaining, it is time to ask for work from B.
BOINC WIKI
John Thanx John for the new
)
John
Thanx John for the new scheduler, just love the refinements that you have added. I too used to be slightly annoyed by the same thing as the origanal poster but knew that it did not really matter since it eventually does go back to it. Been using 5.5.13 since it came out on the alpha site and must say that when the new scheduler comes out in the standard client everyone should be as pleased as I am.
Steve
98SE XP2500+ @ 2.1 GHz Boinc v5.8.8
The OP knew well that it
)
The OP knew well that it didn't really matter as the STD only got knocked back a little and the last minute or so was done after a "short period", but when you have several projects like that, the BOINC Manager window, if it is to show all current work, needs to be a lot larger then it should, because you have a number of wu's littering the display with 1 or less minutes to run.
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
RE: The OP knew well that
)
This is nearly gone with John's new scheduler. Downloading does no longer trigger the cpu scheduler and what I even like more: The "overshooting" of too many new WUs after a break is gone, because the client now asks the server for only so much work as really is needed to fill the queue. If you have multiple projects and you want to have 1 day of work for each project, now you can set the connect interval to "1.0 days".
Norbert
RE: The "overshooting" of
)
I agree, that will be nice to see the back of.
Will the new BOINC core run under WinNT? I still have 5.2.13 on my NT box as someone, I think on the Rosetta board, had trouble with a 5.4.x core.
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
I'm running 5.4.11 on NT4
)
I'm running 5.4.11 on NT4 with no problems.
Alinator