|
1)
Message boards :
Number crunching :
When will you update yafu to version 2?
(Message 1667)
Posted 17 Dec 2022 by vaughan Post: Or at least to a version that fixes the bugs of never ending tasks on Windows application ... I concur. |
|
2)
Message boards :
Number crunching :
When should a "stalled" task be aborted?
(Message 1603)
Posted 20 Apr 2022 by vaughan Post: I aborted a ali task that had run hogging all CPU threads for 3 days 5 hours. Stuck on 100 percent for days. Useless application. |
|
3)
Message boards :
Number crunching :
When should a "stalled" task be aborted?
(Message 1590)
Posted 14 Dec 2021 by vaughan Post: It seems that nobody is reading this thread as no reply from Admin in 2 days. Time to move to another project then. |
|
4)
Message boards :
Number crunching :
When should a "stalled" task be aborted?
(Message 1589)
Posted 12 Dec 2021 by vaughan Post: Why are there so many Yafu tasks that get to 100% but never finish? |
|
5)
Message boards :
Number crunching :
MSG: "Project temporarily unavailable" when adding a new computer
(Message 1480)
Posted 22 Jan 2020 by vaughan Post: I get a message stating "Project temporarily unavailable" when I try to attach another computer to this project. It is a Win10 machine. |
|
6)
Message boards :
Number crunching :
How soon new work?
(Message 817)
Posted 20 Mar 2016 by vaughan Post: Yoyo we are out of work today, please feed us some tasks to crunch. |
|
7)
Message boards :
Number crunching :
Too Late To Validate
(Message 133)
Posted 14 Sep 2011 by vaughan Post: Dear Admin: Your ~1 hour estimate is wrong. I have several computers with YAFU tasks still running well after 1 hour. For example a C2D E6420 @ 2.133GHz has task Yafu_C97_1315917330_94_0 so far at 6 hours 20 minutes and continuing. Progress is stuck on 0.000% (I'm sure I posted about the Progress % not updating but the post seems to have disappeared). Also another Windows 7 machine this time a Core 2 Quad 6600 G0 stepping @ 2.40GHz. It has a C97 task at over 4 hours and still running. What has happened is that the tasks clog up the system so they time out. I checked the E6420 and changed the settings preference so that tasks remain in memory. On the Q6600 this was already set. On the E6420 I reset the project last night as so many tasks were not going to complete. The BOINC estimate was over 4 hours. After the rest stupid thing set the YAFU estimate a 17 minutes - crikey. What happened to the "I increased the estimated time per task" adjustment you made? Better to err on the side of caution like for example CAS@home where the initial tasks are estimated at several hundred hours. This allows BOINC to self correct the run time and you don't have a swag full of tasks cached. I am no mathematician but I don't understand the urgency of this sieving project in getting tasks from a factordb crunched in under 10 hours. If the time-frame is so short why not run the project from GPUs like the PrimeGrid Project does for its PPS sieving sub-project? If it remains as a CPU project then I concur with the other posters and strongly urge the project administrator to increase the time limit to several days. my 2c |
|
8)
Questions and Answers :
Windows :
Task progress indicator?
(Message 124)
Posted 12 Sep 2011 by vaughan Post: The progress indicator in percentage format doesn't change during a task being crunched. All mine stay on 0.000% |
|
9)
Questions and Answers :
Web site :
FIXED: Server Status
(Message 71)
Posted 4 Sep 2011 by vaughan Post: I am receiving tasks to crunch but the server status page shows the Upload / Download server status as Disabled. Clearly it is not. |