Thread 'Multiple start-stop schedule within 24hrs?'

Message boards : BOINC Manager : Multiple start-stop schedule within 24hrs?
Message board moderation

To post messages, you must log in.

AuthorMessage
thinking_goose

Send message
Joined: 1 Nov 15
Posts: 2
United Kingdom
Message 65182 - Posted: 1 Nov 2015, 21:05:03 UTC

Is there a way to make cc_config.xml understand a more complex time schedule than to work within a single time frame? For example:

Work CPU between 23:01 and 25:59;
Work CPU+GPU between 01:01 and 06:59
ID: 65182 · Report as offensive
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 272
Australia
Message 65251 - Posted: 4 Nov 2015, 5:07:47 UTC
Last modified: 4 Nov 2015, 5:09:37 UTC

Depending on your operating system you'd have to use cron (Linux) or the Windows Task Scheduler to turn these modes on and off using the BOINC command line tool

I presume the Mac would have something similar to cron for scheduling tasks.

As mentioned above you are saying run CPU all the time and between 00:01 and 06:59 allow the GPU. So you'd need a BOINCCMD --set_gpu_mode to toggle between always and never. According to the documentation it also has a duration so you might even be able to simply enable it for a duration of ~ 25200 seconds.
MarkJ
ID: 65251 · Report as offensive
thinking_goose

Send message
Joined: 1 Nov 15
Posts: 2
United Kingdom
Message 65275 - Posted: 5 Nov 2015, 12:53:42 UTC - in response to Message 65251.  

I'll be using linux, so I'll look into cron.

The two different time slots are based on my cheap electricity schedule. I want to avoid GPU in the first slot, because I'll probably be using the computer at that time. The second slot is where BOINC can use everything.

From 01:01 to 06:59 (second slot) the cost goes back to cheap rate again, and the one minute difference is there to make sure there is no accidental overlap into expensive time.
ID: 65275 · Report as offensive

Message boards : BOINC Manager : Multiple start-stop schedule within 24hrs?

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.