I am running BOINC v6.10.43 on my Apple iMac computer under Mac OS X 10.6.3 (Snow Leopard).
Just found this on the BOINC site under NEWS:
Quote:
BOINC 6.10.43/44 withdrawn
Due to a bug in .43/.44, the currently stable BOINC client has been rolled back to 6.10.18. The bug in question only affects volunteers using GPUs that do not have enough GPU RAM to execute their desired project applications. This bug is fixed in 6.10.46 or newer.
When you click "Download" you'll automatically receive an earlier version, 6.10.21...not 6.10.18.
Resetting the project may help (Projects > Reset Project). The GC 7.01 project is now running normally again.
I tried resetting the project but it didn't help.
Also, I went back to BOINC Version 6.10.21 after reading VenusEMar's Message 103843, but the problem remains—My Einstein tasks' time "To completion" is still incorrectly going up instead of down, and the "Elapsed" times correctly goes up.
My Einstein tasks' time "To completion" is still incorrectly going up instead of down, and the "Elapsed" times correctly goes up.
Did one of those finish computing?
The symptoms hint at a wrong DCF (Duration Correction Factor), which would be corrected after a task [edit]or several[/edit] has finished.
Gruß,
Gundolf
No, when I reset the project, my 2 work units had been crunching for almost 300 hours collectively.
The 2 new units have been each crunching for over 28 hours, and both show that they have over 96 hours to completion, and the time to completion continues to increase. How can the DCF be corrected if the task never finishes?
The same again: shifting hours, running at high priority. Knocking out World Community + SETI projects. After reading Gundolf's message, I checked my benchmark values:
Measured floating point speed 1027.07 million ops/sec
Measured integer speed 2382.82 million ops/sec
Is this how the project is going to run if this isn't a bug? If so, I won't fuss about this any more.
Is this how the project is going to run if this isn't a bug?
If BOINC has learned how your computer deals with Einstein tasks, all will be normal again, but to do that learning, it has to finish at least one task. After that, the initial estimate will be much more accurate and won't need constant readjusting.
I guess you'll have to wait about 40 hours for one S5GCE task to finish (if running at 100% CPU time).
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
If BOINC has learned how your computer deals with Einstein tasks, all will be normal again, but to do that learning, it has to finish at least one task. After that, the initial estimate will be much more accurate and won't need constant readjusting.
I guess you'll have to wait about 40 hours for one S5GCE task to finish (if running at 100% CPU time).
Ahhhh, finally comprendo! Gundolf, thanks for all your very patient explanations!
RE: I am running BOINC
)
Just found this on the BOINC site under NEWS:
When you click "Download" you'll automatically receive an earlier version, 6.10.21...not 6.10.18.
RE: When you click
)
That depends on your operating system:
for linux it's 6.10.17
for windows it's 6.10.18
and for macs it's 6.10.21
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: Resetting the project
)
I tried resetting the project but it didn't help.
Also, I went back to BOINC Version 6.10.21 after reading VenusEMar's Message 103843, but the problem remains—My Einstein tasks' time "To completion" is still incorrectly going up instead of down, and the "Elapsed" times correctly goes up.
My SETI workunits are crunching normally.
Tracy
RE: My Einstein tasks' time
)
Did one of those finish computing?
The symptoms hint at a wrong DCF (Duration Correction Factor), which would be corrected after a task [edit]or several[/edit] has finished.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: RE: My Einstein
)
No, when I reset the project, my 2 work units had been crunching for almost 300 hours collectively.
The 2 new units have been each crunching for over 28 hours, and both show that they have over 96 hours to completion, and the time to completion continues to increase. How can the DCF be corrected if the task never finishes?
Tracy
RE: How can the DCF be
)
It can, but it's not a recommended procedure.
I think you'll have to be just a bit more patient. My laptop with these benchmark values:
needs about 35 hours for a S5GCE task and the estimates are pretty near to that.
This one of your computers is rated at
That's a factor of 3 to 4. So, I'd expect that computer to need about 105 to 140 hours (at least).
You'll never know the exact time if you don't wait for at least one task to finish.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
The same again: shifting
)
The same again: shifting hours, running at high priority. Knocking out World Community + SETI projects. After reading Gundolf's message, I checked my benchmark values:
Measured floating point speed 1027.07 million ops/sec
Measured integer speed 2382.82 million ops/sec
Is this how the project is going to run if this isn't a bug? If so, I won't fuss about this any more.
RE: RE: How can the DCF
)
Thanks for the info—I'll be patient and let them finish crunching.
I'll let you know what happens...
Tracy
RE: Is this how the project
)
If BOINC has learned how your computer deals with Einstein tasks, all will be normal again, but to do that learning, it has to finish at least one task. After that, the initial estimate will be much more accurate and won't need constant readjusting.
I guess you'll have to wait about 40 hours for one S5GCE task to finish (if running at 100% CPU time).
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: If BOINC has learned
)
Ahhhh, finally comprendo! Gundolf, thanks for all your very patient explanations!