|
1)
Message boards :
Number crunching :
Too many WUs!
(Message 1246)
Posted 31 Aug 2018 by eviltimbert Post: 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. |
|
2)
Message boards :
Number crunching :
Too many WUs!
(Message 1243)
Posted 24 Aug 2018 by eviltimbert Post: 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) |
|
3)
Message boards :
Number crunching :
Too many WUs!
(Message 1241)
Posted 23 Aug 2018 by eviltimbert Post: 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. |
|
4)
Message boards :
Number crunching :
Stuck at 100% for nearly 6 days !!
(Message 1190)
Posted 29 Mar 2018 by eviltimbert Post: I had set up compute restriction hours in the BOINC manager for Saturday and Sunday so the last restart must've been Sunday night which is why it showed 3+ days running. Actually it was probably running for much longer. I only check in on these machines once a week or if I see jobs timing out because of deadlines. |
|
5)
Message boards :
Number crunching :
Stuck at 100% for nearly 6 days !!
(Message 1188)
Posted 29 Mar 2018 by eviltimbert Post: I have the same problem with another machine. Running forever and the gnfs.log file hasn't updated in days. I'll abort it as well. Looks like everyone else running Windows had a problem with this workunit. http://yafu.myfirewall.org/yafu//result.php?resultid=1999222 (2CPUs, 1 instance of gnfs_lasieve running) |
|
6)
Message boards :
Number crunching :
Stuck at 100% for nearly 6 days !!
(Message 1187)
Posted 29 Mar 2018 by eviltimbert Post: I suspended and restarted the task and it reset back to 99.966% (it was sitting at 100%) and the progress time went back to 13hr45min instead of 7+days. It started running 4 instances of gnfs-lasieve and dropped to 1 process again. I'll let it run a couple hours and then abort it. |
|
7)
Message boards :
Number crunching :
Stuck at 100% for nearly 6 days !!
(Message 1185)
Posted 28 Mar 2018 by eviltimbert Post: Yes I thought that was odd too. The gnfs-lasieve4I13e.exe process is still running and using CPU. Since the task says it's consuming 4 CPUs I thought the process would be running 4 times but it's not. That was the only gnfs process running until another 3 CPU YAFU project started up and is running 3 gnfs processes as well. So now I have one 4T task running with one gnfs process that is consuming 34MB of memory. The second standard YAFU task is using 3 CPUs and running three gnfs processes each using 21MB. |
|
8)
Message boards :
Number crunching :
Stuck at 100% for nearly 6 days !!
(Message 1183)
Posted 28 Mar 2018 by eviltimbert Post: Is the 5 day credit extension from the BOINC deadline date or the date on the site? I've got a 4T workunit running over 6 days currently. The BOINC deadline says March 24, the site says March 29. It's still using CPU cycles so I don't want to abort it but the logs seem old. Is there anything else I should check to see that it's doing valid work? |
