My RAC has been stuck at 33 for ages...I haven't run Einstein for many many months (not since it first came out) and therefore I really should have zero RAC by now but I dont...how come?
My RAC has been stuck at 33 for ages...I haven't run Einstein for many many months (not since it first came out) and therefore I really should have zero RAC by now but I dont...how come?
Drezha,
This happens because Boinc does not update your stats until you either run it and click on project "Update" or when you download another WU, in other words, when your Boinc client next communicates with the Einstein server.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
From the BOINC Wiki: The process to update the RAC should be run on a weekly basis, but it is possible that this process may be halted and the RAC will not reflect abrupt terminations of the Participant's computers contributions to a project.
So, if one or more of your machines stops processing work for a project, it is possible that its RAC will remain at a constant value for some period of time and you will not see an expected decay curve. The same effect holds true for when the Project stops accepting returned Results, such as when the Project is suspended.
From the BOINC Wiki: The process to update the RAC should be run on a weekly basis, but it is possible that this process may be halted and the RAC will not reflect abrupt terminations of the Participant's computers contributions to a project.
So, if one or more of your machines stops processing work for a project, it is possible that its RAC will remain at a constant value for some period of time and you will not see an expected decay curve. The same effect holds true for when the Project stops accepting returned Results, such as when the Project is suspended.
Richard
Richard,
The explanation from the Wiki may be how the system was designed to work, but the reality is that there are scads (probably upwards of 100,000) of hosts in the same condition; the server simply does not update RAC until it "sees" the host again. While this is not readily apparent, it may be verified by looking through member stats on virtually any team page (look at members with low total credit and unduly high RAC) - if they're not new hosts, chances are they've not contacted the server for months, yet RAC remains unduly high, i.e., static. This is just an observation, I don't see it as a problem.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Thank god that the "top participants" list doesn't seem to count these "stuck" RACs. Otherwise all you have to do is change ID all the time and get stuck RAC on all computers and have a huge RAC in that list... ;)
OK,I haven't really checked if this statement is true,but I haven't seen anybody whine about it so... sorry for my laziness.. :P
Laziness is nothing more than the habit of resting before you get tired. ~Jules Renard
RAC is very wrong...
)
Drezha,
This happens because Boinc does not update your stats until you either run it and click on project "Update" or when you download another WU, in other words, when your Boinc client next communicates with the Einstein server.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
From the BOINC Wiki: The
)
From the BOINC Wiki: The process to update the RAC should be run on a weekly basis, but it is possible that this process may be halted and the RAC will not reflect abrupt terminations of the Participant's computers contributions to a project.
So, if one or more of your machines stops processing work for a project, it is possible that its RAC will remain at a constant value for some period of time and you will not see an expected decay curve. The same effect holds true for when the Project stops accepting returned Results, such as when the Project is suspended.
Richard
RE: From the BOINC Wiki:
)
Richard,
The explanation from the Wiki may be how the system was designed to work, but the reality is that there are scads (probably upwards of 100,000) of hosts in the same condition; the server simply does not update RAC until it "sees" the host again. While this is not readily apparent, it may be verified by looking through member stats on virtually any team page (look at members with low total credit and unduly high RAC) - if they're not new hosts, chances are they've not contacted the server for months, yet RAC remains unduly high, i.e., static. This is just an observation, I don't see it as a problem.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Thank god that the "top
)
Thank god that the "top participants" list doesn't seem to count these "stuck" RACs. Otherwise all you have to do is change ID all the time and get stuck RAC on all computers and have a huge RAC in that list... ;)
OK,I haven't really checked if this statement is true,but I haven't seen anybody whine about it so... sorry for my laziness.. :P
Laziness is nothing more than the habit of resting before you get tired. ~Jules Renard
so basically I have to
)
so basically I have to connect, crunch some and then leave?
RE: so basically I have to
)
Drezha,
If you really need the account to read zero RAC, all you have to do is connect Einstein, update, and then detach. That should do it.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK