I don't see why folks don't just fill their queue with other work for a day or so in order to ensure a good day of backlog, then change their preference to say 3 or 4 days for OET, and likely in under 24 hours they should catch a nice backlog of OET WUs to crunch on for several days. Then repeat, repeat, repeat.

Is it that hard? I'm sure that is how some of the big crunchers are pushing beyond the 1 year mark already....

I figure I'll do that this Friday to have a weekend crunchathon of OET WUs and in a couple weekends I should hit my bronze badge, then onto higher levels as 2015 unfolds....

Hi Sandvika,

If you have BOINC manager in Simple view, change it to Advanced. Click Tools / Computing preferences in the menu (or something similar to this, I am translating it from the BOINC Slovak language mutation). In tab "Network Usage" you can find "Minimal work reserve" (or similar ) in days, set it to desired cache

The same applies to MAC OS X BOINC manager (version 7.4.x).

Cheers and

How is it possible to get ANY work units. I am running 29 cores 24x7 with both OET and UGM checked. There are crunchers with 5 years complete. I just can't figure out how.

I have received 4 OET WU in the last 5 days. Not 5 days but 4 WU.

My last test was to take my reliable 4-core and run it for 55 clock hours for only OET. Didn't get a single WU. Kind of defeats the purpose of crunching when my computer is idle

@theodolite... easy: Load up your queue with other project WUs (1.5 or 2 days? you decide) and then select the OET only (make sure you don't have the "If there is no work available for the project(s)please send me work from another project" option selected). You can increase your queue to create the need to ask for new work. Here's a another description of the process.

Luck...

CJSL

Crunching for a better world...

Hi Branjo, thanks for your tip. In the mean time I looked in my event log and noticed that whilst BOINC is running jobs it keeps on looking for more work regularly. On the other hand, as soon as it finds no work to do, it lengthens the polling interval each time that it can't find work and it quickly escalates to be hours. Consequently, in those brief periods when OET WUs become available, it is sleeping instead of looking for work! (Projects->Properties: Scheduling: CPU work fetch values) Clicking Projects->Update resets the polling interval, starting at 2 minutes. I started Googling and quickly found a discussion of the BOINC V6 vs V7 scheduler, which led me to editing the global_prefs_override config file and reloading it (Advanced->Read local prefs file).

Then I found your tip and discovered the values I'd set in the config file had been populated into the "network usage" preferences you mentioned Now I see them, it's clear what the fields are for, it just didn't occur to me that scheduler parameters would be set in the networking configuration It's a for usability when the config file is more intuitive than the user interface

I'll see how self-sustaining it becomes once it actually has OET work to do with the new settings. Ideally I don't want to oversubscribe the cores on my PC, so if I can keep it topped up to at least 2 days with either OET or UGM, I can change the device profile in use to get UGM once a day if it is running short and leave it on OET the rest of the time.

Cheers and