Message boards :
Number crunching :
@Markku - Estimated WU Completion
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
![]() Send message Joined: 2 Sep 04 Posts: 165 Credit: 146,925 RAC: 0 |
> Hmm, not sure i understand. > The variable number of turns are tuned in the input files, and the time > estimate(well, actually the fops estimate) is based on the number of turns we > ask to be done. > And the correction factor does its work based on the original (fpops) estimate from the developers, so the estimates that are proportional to some known input value (like LHC has) are no problem at all. The real problem is the projects where the developers have no real idea what the running time is going to be because the inputs are too complex (like Protein Predictor has). After a month or two of the new versions being out in general hands, you should have a good idea how wrong the initial estimates are (take the average correction factor, and you won't be too far off from the % error in the original fpops estimate). ![]() ![]() BOINC WIKI |
![]() Send message Joined: 2 Sep 04 Posts: 165 Credit: 146,925 RAC: 0 |
> > I am waiting for the next recommended release where BOINC "learns" > reality. > > The only fly in the ointment is LHC@Home with the variable number of > turns. > > > > The picture is more involved than this, given that any unit potentially can > terminate in a few seconds or minutes if the beam is unstable. LHC@Home is not > the only project with this sort of variable execution. MDIV units run by a > closed Alpha project that I know Paul is aware of can vary according the the > requirements of the input files. The project's home page suggests that time > estimates may be 'wildly inaccurate'. What's worse, the MDIV units neither > update their progress meters, nor write checkpoint data. I can't see how BOINC > 4.7+ can learn anything effective from either SixTrack or MDIV > Yes, the sudden death problem was taken into account. This is precisely why the estimate is reduced slowly. If a completion time is less than 10% of the midified original estimate, then the estimate will move down even more slowly just so that a few fast returning results will not upset the estimate too much. ![]() ![]() BOINC WIKI |
![]() Send message Joined: 2 Sep 04 Posts: 545 Credit: 148,912 RAC: 0 |
John, Ok, thanks ... I get it now ... :) Then again I have not been at my best this last week (coming out of it??) and so, easily led astray. |
![]() Send message Joined: 22 Oct 04 Posts: 39 Credit: 46,748 RAC: 0 |
Any estimates as to when 4.7+ will be released to the general public or is it too soon to tell? ![]() |
![]() Send message Joined: 2 Sep 04 Posts: 165 Credit: 146,925 RAC: 0 |
> Any estimates as to when 4.7+ will be released to the general public or is it > too soon to tell? > I am a mushroom. ![]() ![]() BOINC WIKI |
![]() Send message Joined: 2 Sep 04 Posts: 545 Credit: 148,912 RAC: 0 |
I thought the line went: "I am the eggman, I am the walrus... koo koo ka choo"? |
Send message Joined: 13 Jul 05 Posts: 169 Credit: 14,978,870 RAC: 115 ![]() ![]() |
> [edit: I just looked at [John's] hosts - oh my you are pushing the > bounds of old and slow machines on BOINC!] Well, I'm jealous - my old and slow machines are on RedHat 6.2, and I can't find a working BOINC client :( (I've compiled several, but the benchmarking always concludes that I have zero, count 'em, ZERO processors installed. Sigh.) Henry |
![]() Send message Joined: 2 Sep 04 Posts: 165 Credit: 146,925 RAC: 0 |
> I thought the line went: "I am the eggman, I am the walrus... koo koo ka > choo"? > Wrong line. I am a mushroom, I must be a mushroom. They keep me in the dark and they feed me BullS****. ![]() ![]() BOINC WIKI |
©2024 CERN