I am no computer wizard. Lately I seem to get this occurring with Milkyway.
Progress does not advance but both "elapsed time" and "estimated remaining" continue to increase.
Is this my machine handling it wrong or something wrong with the task?
Myron

---

I am no computer wizard. Lately I seem to get this occurring with Milkyway.
Progress does not advance but both "elapsed time" and "estimated remaining" continue to increase.
Is this my machine handling it wrong or something wrong with the task?
Myron

Are you letting MilkyWay use all of your cpu cores or just some of them? What do you have for your percentage of cpu usage set at, if you don't know then it's probably at the defaults which I think is 100% which is okay. The problem could be that you are letting MilkyWay use all of your cpu cores so when you do something else with the pc MilkyWay stops and that can cause problems, the User Link will hopefully see this and also respond and maybe even post his xml file that you can plug into MilkyWay and you can use it to restrict the number of cpu cores your pc uses for each task.

In the short term try suspending Boinc and then restart it after maybe 30 seconds and see if the tasks don't start back up again like they should, they COULD back off a bit and pick back up from a restore point so don't be surprised if you see that happen.

Thanks, I will look into that. Seems to run for days without a problem then will get hung up on one task. The remaining time will soon stretch to 60 days or more. This only started occurring in the last couple months. If i abort the task it will be fine again for several tasks.
Cheers!

Thanks, I will look into that. Seems to run for days without a problem then will get hung up on one task. The remaining time will soon stretch to 60 days or more. This only started occurring in the last couple months. If i abort the task it will be fine again for several tasks.
Cheers!

Some tasks do take alot longer than other tasks and Link can probably give you are more definitive answer but the rule of thumb is if the time is running let it run, if it stops running suspend the task for more than 20 seconds and then if that doesn't work shut down Boinc and then restart it to see if the task starts running again or not. If not abort it and move on if it does then let it run. The tasks are looking at a large picture and some have lots of data points in them while others have very little, so giving a definitive time for each task isn't possible.

Thanks,
Just that occasionally the estimated time remaining will start at ...like 30 min or something. I check on it a few hours later and now its a week. Still later it turns to a month. So I abort it.
Appreciate your response!

---

Thanks,
Just that occasionally the estimated time remaining will start at ...like 30 min or something. I check on it a few hours later and now its a week. Still later it turns to a month. So I abort it.
Appreciate your response!

As long as the time is running and not too close to running out of time to send it back then I would let it keep going, sometimes they do come down in time as they get closer to the end, but I too have aborted some that were near the deadline with a month to go.

As far as I can see on the two success tasks you are already limiting n-Body to 4 cores. Do you allow BOINC to use 100% of CPU time? If not, that's likely the issue if the task was indeed stuck, however time estimates for n-Body are sometimes very far away from reality, so what you have seen with time increasing, might simply happen every now and than. In such case simply check if the task is using CPU time, either by opening the "properties" of a task two times and comparing the numbers or in Windows Task Manager.

---

Yes

CPU is set to 100%, but I've limited BOINC to 3 "processors"

I've had two WUs sneak through since making those settings and had three more runaways, We were out of town, and one went to 1,211,658.39 seconds wall clock time

hate to say it, but I've set to "no new work" for now

Yes

CPU is set to 100%, but I've limited BOINC to 3 "processors"

I've had two WUs sneak through since making those settings and had three more runaways, We were out of town, and one went to 1,211,658.39 seconds wall clock time

hate to say it, but I've set to "no new work" for now

Whew that's a LONG time!!! When I run these tasks I limit it to 2 cpu's per task and then run multiple tasks at one time and also have some runaways and do abort them, but I just get another task and keep on crunching. When I go out of town for more than a few days I try to run my pc's dry of tasks but if it's just a few days I too will just let the tasks run so could have a task do what yours did too.