Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • fix_Makefile.mingw#2
  • update_Makefile.mingw
  • fix_Makefile.mingw
  • fix_API_for_C_apps
  • fix_procinfo_mac
  • boinccmd_gpu_mode_always_until_sigterm
  • fgrp_osx_hotfix
  • fix_boinc_master@f8250782
  • eah_wrapper_improvements
  • diagnostics_win-hotfix
  • diagnostics_win-hotfix-old
  • current_fgrp_apps
  • testing_gw_apps
  • gw_app_darwin_15
  • current_brp_apps
  • current_brp_apps_android10
  • current_gfx_apps
  • current_server
  • current_gw_apps
  • previous_fgrp_apps
  • previous_gw_apps
  • testing_brp_apps
  • apps_FGRP3_1.07
  • apps_FGRP3_1.08
25 results

boinc

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    David Anderson authored
        - a project overestimates job FLOP counts
        - the client starts jobs in EDF mode
        - as job progresses and fraction done increases,
            its completion time estimate decreases until
            it's no longer a deadline miss.
        - job gets preempted by other job from that project;
            you end up with lots of partly completed jobs.
        Solution (I hope): if an app version has running jobs,
            compute a "temp DCF" for the app version,
            which is the min of dynamic/static estimates for its jobs.
            Apply this scaling factor to completion time estimates
            for unstarted jobs in RR simulation
    - client: the estimation of remaining time of running jobs was wrong
        (how did this bug survive so long?)
    
    svn path=/trunk/boinc/; revision=20077
    37aae854
    History