I am also having this problem and it just start the other day. I tried restarting bonic and restarting the computer, but still have a problem. This problem is only with the einstein project on this one computer, all other projects are running fine.
The computer is a 2.0ghz AMD Athlon XP with 768MB of ram/memory.
I am also having this problem and it just start the other day. I tried restarting bonic and restarting the computer, but still have a problem. This problem is only with the einstein project on this one computer, all other projects are running fine.
The computer is a 2.0ghz AMD Athlon XP with 768MB of ram/memory.
Are you running the pc 24/7 or are you turning it off at night/day? If you are turning it off that could be your problem. Boinc is designed to run 24/7 and it can have 'issues' if it doesn't. Those issues can be worked around with a few tweaks but by default it can give problems. Also how many projects are you crunching for? That too can be a source of problems, not the projects themselves but how Boinc handles the switching between them.
The computer is running 24/7 and only running boinc. This computer's projects are Einstein@home and MilkyWay@home. The cpu switches between projects every hour.
I was thinking it had something to do with the cpu heating up and how the newer cpu's throttle down to stay cool, but thats not my problem. The completion counter only increases on the einstein@home project.
Boinc is designed to run 24/7 and it can have 'issues' if it doesn't.
What?! And to think so many years I thought BOINC was designed to use unused CPU-cycles when the computer is on, whether running 24/7 or not. I wonder how BOINC on my wife's laptop can handle all those numerous shutdowns/powerups/hibernations every day without errors...
[/sarcasm off]
The computer is running 24/7 and only running boinc. This computer's projects are Einstein@home and MilkyWay@home. The cpu switches between projects every hour.
I was thinking it had something to do with the cpu heating up and how the newer cpu's throttle down to stay cool, but thats not my problem. The completion counter only increases on the einstein@home project.
Does the to-completion counter increase continually?
With my system, it only increases for a minute or so, before it decreases more than it had increased before. I think the cause for this is that the application only so often tells boinc of its progress (every minute or so). So, in between, BOINC thinks that the time to completion rises because no progress seems to be done. [edit] Other projects' applications update their progress more often, so that there you don't get an intermediate increase.[/edit]
Another reason could be a bad Duration Correction Factor (DCF), but that is corrected when a work unit finishes.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Boinc is designed to run 24/7 and it can have 'issues' if it doesn't.
What?! And to think so many years I thought BOINC was designed to use unused CPU-cycles when the computer is on, whether running 24/7 or not. I wonder how BOINC on my wife's laptop can handle all those numerous shutdowns/powerups/hibernations every day without errors...
[/sarcasm off]
It's okay, lots of people do what you do and never see the problems, but when they happen, they happen badly. What usually happens is that a given project saves where you are in crunching thru 'checkpointing', that way when you start back up crunching again you don't have to start over from the beginning. This works just fine in alot of cases but for some projects it does not! On those projects you either start over from the beginning, or it loses where you are totally and it just hangs and never finishes the unit it is on. These are known issues and have been around for awhile now. Mostly it is on projects that use 'wrappers' to make their units work under Boinc. So it is NOT all projects BY FAR that have problems!
The computer is running 24/7 and only running boinc. This computer's projects are Einstein@home and MilkyWay@home. The cpu switches between projects every hour.
I was thinking it had something to do with the cpu heating up and how the newer cpu's throttle down to stay cool, but thats not my problem. The completion counter only increases on the einstein@home project.
Milky Way is having numerous problems right now, could it be just a bad, or bad batch, workunit?
Just to make sure, the task in question is not suspended manually, right? There's a bug in BOINC that will cause the "Time To Completion" increasing after manually suspending a task.
How fast is the time to completion increasing (e.g. like 1:1 with real time) and is the task actually in the "Running" state? Is the (consumed) CPU time increasing as well or is it fixed??
Yes the to-completion counter increase continually and at a 1:1 ratio with real time. However when the progress gets to near 99% done it sometimes stop increasing, but it does not decrease, then starts increasing again (like the counter paused then continued).
I have not had any problems with MilyWay@home and I don't think its related to the einstein@home problem.
When a task is manually suspended the time to completion does Not increase, normal. When running, yes the time elapsed also increases at normal 1:1.
This problem only started just recently on only one of one computers running einstein@home.
Time to Completion
)
You are giving pretty few informations, considering that your computers are hidden.
Did you try a restart of BOINC client or better a reboot?
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
I am also having this problem
)
I am also having this problem and it just start the other day. I tried restarting bonic and restarting the computer, but still have a problem. This problem is only with the einstein project on this one computer, all other projects are running fine.
The computer is a 2.0ghz AMD Athlon XP with 768MB of ram/memory.
RE: I am also having this
)
Are you running the pc 24/7 or are you turning it off at night/day? If you are turning it off that could be your problem. Boinc is designed to run 24/7 and it can have 'issues' if it doesn't. Those issues can be worked around with a few tweaks but by default it can give problems. Also how many projects are you crunching for? That too can be a source of problems, not the projects themselves but how Boinc handles the switching between them.
The computer is running 24/7
)
The computer is running 24/7 and only running boinc. This computer's projects are Einstein@home and MilkyWay@home. The cpu switches between projects every hour.
I was thinking it had something to do with the cpu heating up and how the newer cpu's throttle down to stay cool, but thats not my problem. The completion counter only increases on the einstein@home project.
RE: Boinc is designed to
)
What?! And to think so many years I thought BOINC was designed to use unused CPU-cycles when the computer is on, whether running 24/7 or not. I wonder how BOINC on my wife's laptop can handle all those numerous shutdowns/powerups/hibernations every day without errors...
[/sarcasm off]
RE: The computer is running
)
Does the to-completion counter increase continually?
With my system, it only increases for a minute or so, before it decreases more than it had increased before. I think the cause for this is that the application only so often tells boinc of its progress (every minute or so). So, in between, BOINC thinks that the time to completion rises because no progress seems to be done. [edit] Other projects' applications update their progress more often, so that there you don't get an intermediate increase.[/edit]
Another reason could be a bad Duration Correction Factor (DCF), but that is corrected when a work unit finishes.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: RE: Boinc is designed
)
It's okay, lots of people do what you do and never see the problems, but when they happen, they happen badly. What usually happens is that a given project saves where you are in crunching thru 'checkpointing', that way when you start back up crunching again you don't have to start over from the beginning. This works just fine in alot of cases but for some projects it does not! On those projects you either start over from the beginning, or it loses where you are totally and it just hangs and never finishes the unit it is on. These are known issues and have been around for awhile now. Mostly it is on projects that use 'wrappers' to make their units work under Boinc. So it is NOT all projects BY FAR that have problems!
RE: The computer is running
)
Milky Way is having numerous problems right now, could it be just a bad, or bad batch, workunit?
Just to make sure, the task
)
Just to make sure, the task in question is not suspended manually, right? There's a bug in BOINC that will cause the "Time To Completion" increasing after manually suspending a task.
How fast is the time to completion increasing (e.g. like 1:1 with real time) and is the task actually in the "Running" state? Is the (consumed) CPU time increasing as well or is it fixed??
CU
Bikeman
Yes the to-completion counter
)
Yes the to-completion counter increase continually and at a 1:1 ratio with real time. However when the progress gets to near 99% done it sometimes stop increasing, but it does not decrease, then starts increasing again (like the counter paused then continued).
I have not had any problems with MilyWay@home and I don't think its related to the einstein@home problem.
When a task is manually suspended the time to completion does Not increase, normal. When running, yes the time elapsed also increases at normal 1:1.
This problem only started just recently on only one of one computers running einstein@home.
Any more ideas?
Thanks!