Posts by fractal
|
1)
(Message 1056)
Posted 11 Apr 2013 by fractal Post: Are you running openboinc? I run that on my tablet and it errored out every work unit until I found I have to keep it connected to one and only one network 24x7 or it aborts the work. For me this meant telling the tablet to "forget" the second network in my house as it was switching between them for unknown reasons which caused the work in progress to abort. |
|
2)
(Message 841)
Posted 14 Feb 2013 by fractal Post: I have had that happen a few times on various projects. One click, one shift-click to select all the "ready to run" tasks and clicking on <abort> works wonders. Yeah, it is annoying when it happens and even more if it happens often. But once in a while isn't a big issue. |
|
3)
(Message 598)
Posted 10 Jan 2013 by fractal Post: More is always better for us stats junkies but not if it adversely affects the operation of the server. The current update time is decent as well. Some projects update once a day minutes before the FreeDC clock wraps so Daily stats are 0 on that site unless you happen to refresh during that miniscule window. |
|
4)
(Message 282)
Posted 22 Sep 2012 by fractal Post: The benefit of a shorter deadline in my opinion has nothing to do with people who actually do the work. It is for those systems that take thousands of work units and never touch them. It helps the project and the wingmen to have those units expire sooner so they can be given to a machine that will process them. It also keeps the volunteers who want to get their credits sooner happier. I think a 7 day deadline is reasonable for work that takes 3 hours to complete. Crunchers can easily handle a weekend of downtime on either end with no ill affect. It seems to me to be a win/win suggestion. |
|
5)
(Message 254)
Posted 16 Sep 2012 by fractal Post: 2. I still have boinc manager running on the host OS (windows 7) but am using only 50% of the processors (meaning 1 of the existing 2). This is probably why you are getting inaccurate benchmarks. Stop boinc and anything else that is processor intensive in windows before running benchmarks in the VM if you want accurate benchmark results. |