1. 27 Nov, 2009 1 commit
  2. 12 Nov, 2009 1 commit
  3. 23 Oct, 2009 1 commit
  4. 16 Oct, 2009 2 commits
    • David Anderson's avatar
      - client: the weight of GPU debt in computing total debt should be · e86584f6
      David Anderson authored
          (estimated throughput of all GPUs)/(estimated throughput of all CPUs)
          rather than the ratio of 1 GPU to 1 CPU.
          This change will hopefully cause ratios of granted credit
          to more closely match resource shares.
      svn path=/trunk/boinc/; revision=19311
    • David Anderson's avatar
      - client/scheduler: standardize the FLOPS estimate between NVIDIA and ATI. · fe2a18f2
      David Anderson authored
          Make them both peak FLOPS,
          according to the formula supplied by the manufacturer.
          The impact on the client is minor:
          - the startup message describing the GPU
          - the weight of the resource type in computing long-term debt
          On the server, I changed the example app_plan() function
          to assume that app FLOPS is 20% of peak FLOPS
          (that's about what it is for SETI@home)
      svn path=/trunk/boinc/; revision=19310
  5. 14 Oct, 2009 1 commit
  6. 12 Oct, 2009 1 commit
    • David Anderson's avatar
      - client: on startup, if a coproc needed by a job is missing, · 5e862ac4
      David Anderson authored
              set a "coproc_missing" flag rather than aborting the job.
              If use removes a GPU board while there's a large queue of GPU jobs,
              they'll stay queued (until their deadline passes).
              Note: this doesn't fix the situation where user connects via
              Remote Desktop while GPU jobs are running or queued.
              We should check for Remote Desktop every minute or so, and stop GPU jobs.
      svn path=/trunk/boinc/; revision=19287
  7. 03 Oct, 2009 1 commit
  8. 28 Sep, 2009 1 commit
    • David Anderson's avatar
      - client/scheduler/web: add per-project preferences for whether · 71c7e7a7
      David Anderson authored
          to accept CPU, NVIDIA and ATI jobs.
          These prefs are shown only where relevant:
          e.g., only for processor types for which the project has app versions,
          and if it has versions for only one type, no pref is shown.
          These prefs affect both client and scheduler.
          The client won't ask for work for a device blocked by prefs,
          and the scheduler won't send it.
          This replaces earlier optional project-specific prefs for
          "no CPU jobs" and "no GPU jobs".
          (However, these prefs continue to be honored on the server side).
      - client: if NVIDIA driver is unknown, say that rather than 0
      svn path=/trunk/boinc/; revision=19194
  9. 21 Sep, 2009 1 commit
  10. 18 Sep, 2009 1 commit
  11. 16 Sep, 2009 1 commit
    • David Anderson's avatar
      - client and scheduler RPC: add optional <cpu_backoff>, <cuda_backoff>, · 41e3b06b
      David Anderson authored
          and <ati_backoff> elements to scheduler reply.
          These specify backoffs for the resource types,
          overriding the existing backoff mechanism.
          Projects can supply these if they don't have apps of a particular type
          and don't want to get periodic requests for them.
      svn path=/trunk/boinc/; revision=19059
  12. 09 Sep, 2009 1 commit
    • David Anderson's avatar
      - client: fix bug in RR simulation: · f5a6f862
      David Anderson authored
          start only enough jobs to fill CPUs per project,
          not all the CPU jobs at once.
          I'm not sure how much difference this makes,
          but this is how it's supposed to work.
      - client: if app_info.xml doesn't specify flops,
          use an estimate that takes GPUs into account.
      - client: if it's been more than 2 weeks since time stats update,
          don't decay on_frac at all.
      svn path=/trunk/boinc/; revision=19035
  13. 08 Sep, 2009 1 commit
  14. 03 Sep, 2009 1 commit
  15. 02 Sep, 2009 1 commit
  16. 31 Aug, 2009 1 commit
  17. 28 Aug, 2009 2 commits
  18. 17 Aug, 2009 1 commit
  19. 14 Aug, 2009 1 commit
  20. 22 Jul, 2009 1 commit
  21. 17 Jul, 2009 1 commit
    • David Anderson's avatar
      - client: 2nd try on my last checkin. · 57531539
      David Anderson authored
          We need to estimate 2 different delays for each resource type:
          1) "saturated time": the time the resource will be fully utilized
              (new name for the old "estimated delay").
              This is used to compute work requests.
          2) "busy time": the time a new job would have to wait
              to start using this resource.
              This is passed to the scheduler and used for a crude deadline check.
              Note: this is ill-defined; a single number doesn't suffice.
              But as a very rough estimate, I'll use the sum of
                  (J.duration * J.ninstances)/ninstances
              over all jobs that miss their deadline under RR sim.
      svn path=/trunk/boinc/; revision=18629
  22. 16 Jul, 2009 1 commit
    • David Anderson's avatar
      - client: change the way a resource's "estimated delay" · 8a1c0816
      David Anderson authored
          (passed to server for crude deadline check) is computed.
          Old: estimated delay is the interval for which the resource
              is fully used (i.e., all instances busy).
          Problem: this may cause unnecessary project starvation.
              example: 1 CPU machine, has a month-long CPDN job
              with a 1-year deadline (it's not in deadline trouble).
              Then the CPU estimated delay will be 1 month,
              and the client won't get any work from projects
              with deadlines shorter than 1 month.
          New: estimated delay is the latest time at which the
              resource is fully used and is being used by at least 1 job
              that is projected to miss its deadline under RR.
          Note: this isn't precise, but I don't think we can improve it
          much without getting a lot more complex.
      svn path=/trunk/boinc/; revision=18607
  23. 07 Jul, 2009 1 commit
  24. 02 Jun, 2009 2 commits
  25. 11 May, 2009 1 commit
  26. 24 Apr, 2009 1 commit
  27. 10 Apr, 2009 1 commit
    • David Anderson's avatar
      - client: instead of scheduling coproc jobs EDF: · cf638ae3
      David Anderson authored
          - first schedule jobs projected to miss deadline in EDF order
          - then schedule remaining jobs in FIFO order
          This is intended to reduce the number of preemptions of coproc jobs,
          and hence (since they are always preempted by quit)
          to reduce the wasted time due to checkpoint gaps.
      - client: the CPU scheduling policy made use of the number
          of deadline misses in various places.
          This should include only the deadline misses of CPU jobs.
          So move "deadlines_missed" from RR_SIM_STATUS and PROJECT
          to RSC_PROJECT_WORK_FETCH so that we have separate counts
          for CPU and coproc jobs, and use the count for CPU jobs.
      - GUI RPC: removed the rr_sim_deadlines_missed field
          from project descriptor.
          This is no longer meaningful, and it didn't seem to be used anywhere.
      svn path=/trunk/boinc/; revision=17785
  28. 03 Apr, 2009 1 commit
  29. 30 Mar, 2009 1 commit
    • David Anderson's avatar
      - boinc_submit (single-job submission): · f90871a1
      David Anderson authored
          set the job params to reasonable values (see below),
          and make it easy to change these values in the script
      - create_work (function and script): change default job params:
          FLOPs est: 1e9 => 3600e9
          FLOPs bound: 1e10 => 86400e9
          mem bound 100MB => 500MB,
          disk bound 100MB => 1GB
          delay bound: 100000s => 1 week
      svn path=/trunk/boinc/; revision=17703
  30. 28 Mar, 2009 1 commit
  31. 26 Mar, 2009 1 commit
  32. 25 Mar, 2009 1 commit
  33. 19 Mar, 2009 1 commit
  34. 18 Mar, 2009 1 commit
    • David Anderson's avatar
      - client: consider fetching work from overworked projects · 88a44828
      David Anderson authored
          if resource is saturated for < work_buf_min()
          (rather than saturated for 0).
          So now the only significance of "overworked" is that we
          won't ask overworked projects for work if resource is saturated
          more than work_buf_min() but less than work_buf_total()
      svn path=/trunk/boinc/; revision=17620
  35. 03 Mar, 2009 1 commit
  36. 01 Mar, 2009 1 commit
    • David Anderson's avatar
      - client: if we're going to do a scheduler RPC for reasons · ebbf9d56
      David Anderson authored
          other than work fetch (e.g., user request, project request)
          temporarily clear resource backoffs while deciding
          whether to request work.
          The backoffs are there only to delay RPCs,
          and we're going an RPC anyway.
      svn path=/trunk/boinc/; revision=17416
  37. 27 Feb, 2009 1 commit