So that's Tim, Mikee, Neil and me onboard. any other takers?
Tasks have a five day deadline so anything with a due date after 00:01 on the fourth can be bunkered.
Change the Boinc cache settings to "Store at least 10 days" and "Store up to an additional 10 days".
Even with this I've noticed that the project limits the number of tasks to eight per core which isn't long enough for a five day bunker (unless you're running on something like a Pi or an Atom!)
The easiest way around it is to claim to have more cores while you stock up on tasks.
On my i7, the tasks take about 4:45 (4.75 hours)
So to stock up, I'd need to claim to have (number_of_actual_cores * number_of_days * 24)/(tasks_per_core * task_duration) = 8 * 5 * 24 / (8 * 4.75) = 26 cores.
cc_config.xml (in the 'data' directory.)
Code: Select all
<options>
<ncpus>26</ncpus>
</options>
The project limits the total number of tasks to 512 so there's no point in claiming to have more than 64 cores.
It's also worth adding an app_config.xml file while you load up or they'll all try to run at once!
app_config.xml (in the project directory.)
Code: Select all
<app_config>
<project_max_concurrent>N</project_max_concurrent>
</app_config>
Where 'N' is the number of cores you want to crunch on.
Once you've got enough tasks, turn off network access and put the <ncpus> setting and the cache settings back to normal.
The other advantage to bunkering is that the tasks need a wingman so if you started them five days ago then it's likely that the other result has already been uploaded and you'll get the credits immediately.
Turn network access back on once the challenge starts and watch the credits roll in
Mark