Okay, yesterday I updated my secondary cruncher, which uses the GPU only (and doesn't do AP for Seti because it uses too much CPU) to the latest recommended version of Boinc (not the current Beta).
At the time, it had no Einstein work on board. It immediately contacted Einstein and downloaded 13 new tasks, and immediately started running one of them at high priority. It has now returned 4 of the 13 tasks. (After that, I put it on NNT for both projects so it will run out the Setis before I upgrade Lunatics.)
Seems to me, if a task has to go HP the moment it's downloaded, its deadline is too short, or something is still wonky with priority management.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
i am by no means a pro, but. head over to your boinc directory. copy client_state.xml some where so you can open it with out worrying. now, search for duration_correction_factor, you should have one for each project. what are they? im thinking these numbers got all out of whack some how. or one of the other time settings got fubard some how. so id post the DCF and some of the other time stats, heres a block from mine for reference, keep in mind though ive had einstein suspended for about a month while i was trying to work out a solution to a heat issue.
2.413898
this is found in the project nest, do not post this entire nest, it contains hash codes.
if one of these got fubard some how it could throw things out of whack. sadly i have no idea what those should be. but posting the info may help one of the folks here that are much much wiser than me help you.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
The "duration correction factor" or DCF is used to correct the estimated time to completion. If the estimate was spot on the DCF would be 1. If it was to short, as was the case when FGRP4 was launched, it would inflate and become bigger and vice versa if the estimate was to long.
The number is updated every time a task is completed. I usually see something between 1.3 and 2 for Einstein.
The time stats are fractions of time when the computer was turned on, connected to the Internet, processing was allowed and so on. It's used to calculate if a tasks is in danger of missing it's deadline and how much work to ask for to fill the cache.
i am by no means a pro, but. head over to your boinc directory. copy client_state.xml some where so you can open it with out worrying. now, search for duration_correction_factor, you should have one for each project. what are they? im thinking these numbers got all out of whack some how. or one of the other time settings got fubard some how. so id post the DCF and some of the other time stats, heres a block from mine for reference, keep in mind though ive had einstein suspended for about a month while i was trying to work out a solution to a heat issue.
2.413898
this is found in the project nest, do not post this entire nest, it contains hash codes.
The DCF can also be found, in the newer versions, of the Boinc Manager under Projects and then Properties. Scroll all the way down to the bottom and you can see the number listed. It IS possible to reset it thru an xml file setting or you can even use Notepad to do it. BUT the Notepad way CAN be problematic if you change the wrong thing and mess it all up!! Boinc WILL adjust the DCF on its own if you just leave it alone, but it can take days weeks or even months depending on MANY factors. Some of us like it fixed NOW so have learned other ways, but the BEST way is to let Boinc figure it out all by itself.
ps not ALL projects list their DCF under properties, on my laptop here only 3 out of 4 projects have it listed.
The DCF can also be found, in the newer versions, of the Boinc Manager under Projects and then Properties.
Ah, yes, indeed! Nice, I never noticed it being available there, probably because I never looked at that screen in the first place. Thank you for pointing that out.
Okay, yesterday I updated my
)
Okay, yesterday I updated my secondary cruncher, which uses the GPU only (and doesn't do AP for Seti because it uses too much CPU) to the latest recommended version of Boinc (not the current Beta).
At the time, it had no Einstein work on board. It immediately contacted Einstein and downloaded 13 new tasks, and immediately started running one of them at high priority. It has now returned 4 of the 13 tasks. (After that, I put it on NNT for both projects so it will run out the Setis before I upgrade Lunatics.)
Seems to me, if a task has to go HP the moment it's downloaded, its deadline is too short, or something is still wonky with priority management.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
RE: Seems to me, if a task
)
Or this project doesn't have enough resource share allocated to it for the taks to be completed in time, without going into high priority.
Claggy
RE: RE: Seems to me, if a
)
Then shouldn't it just ask for less work in the first place?
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
i am by no means a pro, but.
)
i am by no means a pro, but. head over to your boinc directory. copy client_state.xml some where so you can open it with out worrying. now, search for duration_correction_factor, you should have one for each project. what are they? im thinking these numbers got all out of whack some how. or one of the other time settings got fubard some how. so id post the DCF and some of the other time stats, heres a block from mine for reference, keep in mind though ive had einstein suspended for about a month while i was trying to work out a solution to a heat issue.
this is found in the project nest, do not post this entire nest, it contains hash codes.
0.993702
1.000000
0.998718
0.998718
0.998652
1409004424.881340
275291.929359
1409279709.794716
84617.666692
1353346.885388
1409279715.894035
348667.062576
121334240.482159
1409266489.111265
if one of these got fubard some how it could throw things out of whack. sadly i have no idea what those should be. but posting the info may help one of the folks here that are much much wiser than me help you.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
The "duration correction
)
The "duration correction factor" or DCF is used to correct the estimated time to completion. If the estimate was spot on the DCF would be 1. If it was to short, as was the case when FGRP4 was launched, it would inflate and become bigger and vice versa if the estimate was to long.
The number is updated every time a task is completed. I usually see something between 1.3 and 2 for Einstein.
The time stats are fractions of time when the computer was turned on, connected to the Internet, processing was allowed and so on. It's used to calculate if a tasks is in danger of missing it's deadline and how much work to ask for to fill the cache.
RE: i am by no means a pro,
)
The DCF can also be found, in the newer versions, of the Boinc Manager under Projects and then Properties. Scroll all the way down to the bottom and you can see the number listed. It IS possible to reset it thru an xml file setting or you can even use Notepad to do it. BUT the Notepad way CAN be problematic if you change the wrong thing and mess it all up!! Boinc WILL adjust the DCF on its own if you just leave it alone, but it can take days weeks or even months depending on MANY factors. Some of us like it fixed NOW so have learned other ways, but the BEST way is to let Boinc figure it out all by itself.
ps not ALL projects list their DCF under properties, on my laptop here only 3 out of 4 projects have it listed.
RE: The DCF can also be
)
Ah, yes, indeed! Nice, I never noticed it being available there, probably because I never looked at that screen in the first place. Thank you for pointing that out.