Yep, the longer the intervall is, the more WUs are stored by your computer. It can take a few days until the intervall is met in a realistic way, though, because estimated finishing times are usually not very accurate at first.
They weren't for me. I went back to 1 day, though, because the box running Malaria Control got problems meeting the deadlines. So if you're running multiple projects, especially those with tight deadlines and WUs of very different sizes, you should be a bit careful. No problems with Einstein, though.
Well my experience with a 3 day cache and sharing time between EAH and SAH with a biased split was even the 550 PIII had no trouble at all. It does mean that 5.8.x versions follow what a human might do for scheduling even less than before, but it still honors the resource share split over timeframes of a month or so and keeps the cache fuller AFAICT.
Queuing Tasks in E@H
)
Change your general preferences (Your Account-page) and increase
the "Connect to network about every" interval.
Select E@H project in BOINC client and hit "update".
Michael
Team Linux Users Everywhere
Yep, the longer the intervall
)
Yep, the longer the intervall is, the more WUs are stored by your computer. It can take a few days until the intervall is met in a realistic way, though, because estimated finishing times are usually not very accurate at first.
Agreed, work the cache up
)
Agreed, work the cache up slowly in small steps so BOINC can learn how you use your machine and adjust it's work requests accordingly.
Alinator
Thanks for the
)
Thanks for the replies!
Ive set the interval to 2 days.
And remember the work fetch
)
And remember the work fetch code in the scheduler is much different in 5.8.x and is very sensitive to the length of the deadline.
But 2 days shouldn't be enough to freak out the scheduler.
Kathryn :o)
Einstein@Home Moderator
They weren't for me. I went
)
They weren't for me. I went back to 1 day, though, because the box running Malaria Control got problems meeting the deadlines. So if you're running multiple projects, especially those with tight deadlines and WUs of very different sizes, you should be a bit careful. No problems with Einstein, though.
Well my experience with a 3
)
Well my experience with a 3 day cache and sharing time between EAH and SAH with a biased split was even the 550 PIII had no trouble at all. It does mean that 5.8.x versions follow what a human might do for scheduling even less than before, but it still honors the resource share split over timeframes of a month or so and keeps the cache fuller AFAICT.
Alinator