Message boards :
Number crunching :
Too many WUs!
Message board moderation
Author | Message |
---|---|
CCPLogibro Send message Joined: 11 Feb 18 Posts: 2 Credit: 819,242 RAC: 0 |
I noticed Yafu recently decided to give me more than 3 jobs. Since I only had 16T selected, Yafu gave me more jobs than I'll be able to complete. Since each job takes 1-2 days, can I just cancel out ones that will expire with no credit loss? I'm worried that canceling jobs will lower my credit for finished jobs somehow. Side note, I had some jobs give me, "Error While Computing" results. Any tips on how to alleviate this? |
mikey Send message Joined: 13 Apr 17 Posts: 16 Credit: 14,952,152 RAC: 1,100 |
I noticed Yafu recently decided to give me more than 3 jobs. Since I only had 16T selected, Yafu gave me more jobs than I'll be able to complete. Since each job takes 1-2 days, can I just cancel out ones that will expire with no credit loss? I'm worried that canceling jobs will lower my credit for finished jobs somehow. Yes you can abort workunits you can't finish in time. To alleviate this try lowering your cache in the Boinc Manager, open the Boinc Manager which is down by the clock, then go to options, computing preferences, then in the bottom section are your cache settings, set them to say 0.5 days for the 'store at least' and then 0.5 for the 'store an additional' days of work, be sure to click save at the bottom of that page so your settings are saved. That will give you roughly one day of work and when you need more Boinc will automatically get more. |
eviltimbert Send message Joined: 13 Dec 17 Posts: 8 Credit: 8,740,012 RAC: 0 |
That cache setting relies on BOINC calculating an accurate completion time. Yafu jobs run much longer than BOINC calculates. The only way would be to limit actual number of jobs retrieved and I don't see a setting for that in BOINC or in cc_config.xml options. <fetch_minimal_work> comes close, but it only restricts the number of jobs to the number of CPUs. |
mikey Send message Joined: 13 Apr 17 Posts: 16 Credit: 14,952,152 RAC: 1,100 |
That cache setting relies on BOINC calculating an accurate completion time. Yafu jobs run much longer than BOINC calculates. The only way would be to limit actual number of jobs retrieved and I don't see a setting for that in BOINC or in cc_config.xml options. <fetch_minimal_work> comes close, but it only restricts the number of jobs to the number of CPUs. If you use a zero resource share it will only get one workunit per cpu that you allowed to get work in Boinc. For instance I have a 6 core cpu but am only allowing to use 99% of the cpu's so it gets 5 workunits. I reserve one cpu core to keep the gpu fed for the gpu workunits, from another project, I also do. |
eviltimbert Send message Joined: 13 Dec 17 Posts: 8 Credit: 8,740,012 RAC: 0 |
That cache setting relies on BOINC calculating an accurate completion time. Yafu jobs run much longer than BOINC calculates. The only way would be to limit actual number of jobs retrieved and I don't see a setting for that in BOINC or in cc_config.xml options. <fetch_minimal_work> comes close, but it only restricts the number of jobs to the number of CPUs. Right... but they've got at least 16 cores and don't want more than 2-3 jobs at a time (definitely not 16) |
mikey Send message Joined: 13 Apr 17 Posts: 16 Credit: 14,952,152 RAC: 1,100 |
That cache setting relies on BOINC calculating an accurate completion time. Yafu jobs run much longer than BOINC calculates. The only way would be to limit actual number of jobs retrieved and I don't see a setting for that in BOINC or in cc_config.xml options. <fetch_minimal_work> comes close, but it only restricts the number of jobs to the number of CPUs. They could use this setting under 'Preferences' "Max # of jobs for this project". I also use the setting "Max # of CPUs for this project" and set it to 2 so only 2 cpu cores are used per workunit. |
eviltimbert Send message Joined: 13 Dec 17 Posts: 8 Credit: 8,740,012 RAC: 0 |
They could use this setting under 'Preferences' "Max # of jobs for this project". There's the answer we needed. The Max # of jobs setting under YAFU preferences is probably what they need. Thanks. |