The many aborts in my list consist of my try to find the problem. The aborts did NOT appear in fact of a problem. Now I see that I get slightly more work if I set BOINC to 5 days. It seems that settings highter than 5 days are being ignored. When the next beta of BOINC will be available, I hopefully don´t need to make so much experiments and aborts again.
OK, just checking. ;-)
I suggest you let BOINC stabilize at the 5 day setting for awhile (maybe a week or 10 days). If you find that's still not enough of a reserve, then try upping in say half day increments until you get to where you want for a cache.
The many aborts in my list consist of my try to find the problem. The aborts did NOT appear in fact of a problem. Now I see that I get slightly more work if I set BOINC to 5 days. It seems that settings highter than 5 days are being ignored. When the next beta of BOINC will be available, I hopefully don´t need to make so much experiments and aborts again.
How long were you waiting after changing the cache settings before you started aborting WUs? I've found that several downloads (usually spaced 1 minute apart) are required in order to fill a large cache. My own 0.5 day cache may require up to four downloads to fill if all the WUs are short units, as it appears that work requests are filled in increments of three or four long WUs or ten short WUs. If I set it for seven days, several downloads are required to fill that size of a cache. So, at the least, you could be waiting for over ten minutes until all the work is requested and your cache is filled. Check your message tab--you'll see it requesting more work at one minute intervals until the cache is full.
Main point: setting your cache doesn't mean that all the work to fill it will be downloaded at the same time. Work will be downloaded in separate 3 or 4 long unit (10 short unit) increments until the cache is full, a process that could take 10< minutes.
RE: The many aborts in my
)
OK, just checking. ;-)
I suggest you let BOINC stabilize at the 5 day setting for awhile (maybe a week or 10 days). If you find that's still not enough of a reserve, then try upping in say half day increments until you get to where you want for a cache.
Alinator
RE: The many aborts in my
)
How long were you waiting after changing the cache settings before you started aborting WUs? I've found that several downloads (usually spaced 1 minute apart) are required in order to fill a large cache. My own 0.5 day cache may require up to four downloads to fill if all the WUs are short units, as it appears that work requests are filled in increments of three or four long WUs or ten short WUs. If I set it for seven days, several downloads are required to fill that size of a cache. So, at the least, you could be waiting for over ten minutes until all the work is requested and your cache is filled. Check your message tab--you'll see it requesting more work at one minute intervals until the cache is full.
Main point: setting your cache doesn't mean that all the work to fill it will be downloaded at the same time. Work will be downloaded in separate 3 or 4 long unit (10 short unit) increments until the cache is full, a process that could take 10< minutes.