Posts by Vampus

1) Message boards : SZTAKI Desktop Grid : Exaggerated to completion estimation (Message 7068)
Posted 3573 days ago by Vampus
A reset will probably reinitialize the RDCF, but I’m not sure.

From personal experience, a Project Reset (either Reset or Detach & Reattach) will reset the RDCF (Result Duration Correction Factor) to 1.000000

If you want to try it, make sure you have no SDG work on your host (whether in progress or completed) because all the files in the project folder will be deleted.

This doesn\'t matter in resetting the RDCF, but it does matter for resending Work Units (WU\'s); some projects consistently resends WU\'s (SETI@Home is a \'crap-shoot\' in my recent experience).

After finishing and reporting all the SZTAKI WU\'s, I reset, and it does indeed reset the RDCF. The figure still seems a little blown out, but it\'s a lot easier to recover from 10 hours than from 40 hours :) Thanks for the assist and info.
2) Message boards : SZTAKI Desktop Grid : Old WU\'s w/o credit (Message 7067)
Posted 3573 days ago by Vampus
What is the possibility of gettting some of my old WU\'s that are pending to get credited?????


Judging from that sig, I don\'t think you need them! Sorry, nothing constructive to add, I just feel put to shame :)
3) Message boards : SZTAKI Desktop Grid : Exaggerated to completion estimation (Message 7053)
Posted 3576 days ago by Vampus
Thanks for that Odysseus. So the only check and balance against \"Monster tasks\" is the slow readjustment? But that the only real negative side effect is less WU\'s downloaded at one time, and thus more connectivity? Would resetting the project also reset the RDCF? And for that matter, based on what you\'ve said, doe s it even matter?

I believe this self corrects, albeit very slowly?

Yes. It’s based on the host’s RDCF for the project (which you can check on your computer-summary page, right at the bottom of the time stats: “Result duration correction factor”). This is multiplied by the project’s estimate of each task’s running time on a reference system and divided by the host’s relative benchmark performance (vaguely speaking: I don’t know the exact procedures involved) to produce the figure you see in the Tasks panel.

BOINC is conservative in evaluating RDCF, meaning that it tries to avoid downloading work that won’t be completed on time. An unusually long-running task pushes the figure up much more than a short one brings it down. But it will eventually converge on a sensible value, given a consistent run of performance data.

I seem to be getting consistent 40+hour estimates, which scale down as time goes on, for WU\'s which take no more than 2 hours to complete. Do these false estimates impact my ability to get more WU\'s from Sztaki and other projects?

It will have no effect on other projects. (Check your host pages elsewhere: you’ll see they’re all different, depending in part on how apt a given CPU architecture is for the specific computational requirements of each science app, and how efficiently these were compiled for it.) All it means WRT this project is that you’ll take on less work at a time than your connection-interval and cache settings suggest. RDCF has no part in the debt calculations that determine how much time is spent on each project, according to your resource share, and a high score won’t inhibit BOINC from asking for at least one task at a time. At worst, your host will need to contact the servers more often than you’d expect: unless you’re on a dial-up connection that shouldn’t be an inconvenience.

What causes this?

See above. Although the most recent search application seems pretty well-behaved—touch wood!—earlier versions had wildly unpredictable running times. Your computer probably has ‘bad memories’ of some monster tasks it crunched here in the past. And the current tasks may still be variable enough to prolong the settling-down period.

How can I fix it? And how can I prevent it happening?

You can ‘hack’ the relevant XML files in your BOINC folder to restore a more realistic figure, but it’s not without risk to the stability of your BOINC client, and I wouldn’t recommend it unless you know exactly what you’re doing. I have a G4/400 Mac with a DCF of 65 or something—its tasks start out showing hundreds of hours to complete—but it’s crunching away nonetheless.


4) Message boards : SZTAKI Desktop Grid : Exaggerated to completion estimation (Message 7048)
Posted 3577 days ago by Vampus
Hi Guys. I\'ve been boinc-ing for some time, but I\'m not very savvy on the technical side of it all. Currently, I\'m running NumSys Search 2.06, and it\'s giving me grossly exaggerated \"to completion\" estimations.

I believe this self corrects, albeit very slowly? I seem to be getting consistent 40+hour estimates, which scale down as time goes on, for WU\'s which take no more than 2 hours to complete. Do these false estimates impact my ability to get more WU\'s from Sztaki and other projects? What causes this? How can I fix it? And how can I prevent it happening?


Home | My Account | Message Boards


Copyright © 2017 SZTAKI Desktop Grid