I have preferences set to 24 hours crunching but 327442297 has now been crunching for 38 hours and is stuck at 60.034% although still clocking time up and the time to go is rising in proportion.

Should this be terminated? Is there any way it can be made to terminate without losing the results?

Mike

The properties of that task will show you the CPU time used. Check it, jot down the time, then a minute later check it again. Did it use any CPU time during that minute? I am doubtful the task is getting any CPU time. If it were, the watchdog would have already caught the problem and reported the task result. So, I'm guessing you may have to suspend and then resume the task to get it back to using CPU time. It will probably then run through it's originally expected 24 hour runtime (i.e. another 8-10 hours).

I am using a dual-core 3800+ with Vista Premium and Boinc 6.2.19.

If I have a mini 1.40 & Beta 5.98 running and suspend the project, both tasks are shown as suspended by user. However, the mini 1.40 keeps on running, albeit slowly.

Two other tasks start to run, one at normal speed and the other slowly.

Obviously, one of the new tasks is running on its own in one core and the other new task is sharing the second core with mini 1.40.

I have never seen a core sharing before. Is this ok, or is this a problem. None of my other projects show any signs of this phenomenum.

Any ideas?

There has been a few problems I have experienced and others have as well with 1.4 tasks not suspending, that was mostly in the loopbuild tasks. I have found that you have to just exit boinc and restart it. you may also have to reboot your system. but that is probably last ditch. After one or both of these steps boinc mgr will act properly again.

Check your processes running in task manager by pressing control, alt, delete. Do you show more than the normal number of tasks running?

Mike, if everyone had the same time preference, and if all tasks had roughly the same time per model, what you say would certainly be done. But neither is the case. Some people want shorter times (and, yes, it would be nice if they never received a task that took longer then that, but it's not a perfect world). The mixture of work varies over time. The ratio of long to short model tasks varies. ...and you are correct, this can (and does) throw off the estimates and confuse BOINC about how much work to get.

The best way to get a fairly concistent and predictable completion time is to go the 24hr maximum runtime preference. But, if your machine is only on 2 hours a day, it would take you more then 10 days to complete a task and it would never get returned before the deadline. ...there's always something. But if BOINC is running 24hrs a day anyway, then this will offer the most predictability for human, and BOINC.

Version 5.93 reached 96% plus on a WU showing 10 mins to go. An hour later 97% and 10 mins to go. Stopped BOINC and restarted the WU came up at 97% and when computation restarted reset to zero and 6 hours 20 remaining! Sigh Any ideas?

Ideas? Yes, don't stop BOINC. Seriously.

The fact that your % complete reset to zero implies that no checkpoint was reached during the calculations. Some types of work are able to checkpoint very frequently, some are not.

The time to completion is an estimate, and not always a very accurate estimate. Some of the work they are sending out can take 5 or 6 hours to complete a single model (longer on a slower machine). This is especially true for the 1zpy's. If your preferred runtime is less then this, you will see an estimated time to completion of something under 10 minutes for any time over your preference. So if your preference is the default 3hrs for example, it will show 10min to complete, with expoentially small reductions in that time for the last 2 or 3 hours of the model.

...with your major project (50%) not giving new work, BOINC will have a challenge scheduling work. If LHC should come online tomorrow, BOINC would prefer (based on the debts) to get work for LHC (my guess), and so it's still holding out for that to happen. But, as time goes by and that does not happen, it will be adding to Rosetta debt. So it all balances out.

When you run 5 projects like that, it's normal to not always have work for all of them at the same time. From the sounds of it, once WCG gets work completed, BOINC will request work from Rosetta. Try to resist the temptation to try and force BOINC to do something it doesn't want to do. It will likely only confuse things further.

Mike, it's possible your other projects got enough work that BOINC doesn't think you will have any time to be running Rosetta within your "connect to network every... days" setting.

Please review this thread . It has a number of things to check on your end.

Anyone know why Ralph has been down all day?

Hmmm, the system is down. I'm not on campus today - I'll see if I can get someone there to take a quick look...

-KEL