6.6.4

Aus BC-Wiki
Wechseln zu: Navigation, Suche

Zur Übersicht

  • GUI RPC: the "get all projects" RPC now also returns account managers
  • GUI RPC: Fix compiler warning (missing return value).
  • MGR: Provide a way for skin creators to suppress error messages for missing resources
  • MGR: Save and Restore the last email address/user id used to attach to a project or account manager
  • client: if user requests RPC, do it even if project is backed off
  • manager: show backoff interval correctly
  • client: update LTD correctly
  • MGR: Add a virtual list box to display available account managers.
  • MGR: Filter project list so that it shows only projects supported by the core client
  • MGR: call UpdateSelection() from OnListRender() instead of from RestoreSelections(). Fixes #837.
  • MGR: Suppress Skin Manager error messages by default; enable them only if the Manager is launched from the command line with an argument -c or --checkskins.
  • Client: compute estimated delay (i.e. time until non-saturation) for coprocessors as well as CPU. Send them in scheduler request as part of coproc descriptor.
  • client: fixed bug that computed CPU estimated delay incorrectly
  • client: the work request (req_secs) for a resource is the min of the project's share and the shortfall
  • client: computation of # idle CUDA instances was wrong
  • client: tweak work fetch messages
  • client: buffer 2000 messages instead of 1000
  • client: work fetch fixes
  • client: there was a problem with how the round simulator worked in the presence of coprocessors. The simulator maintained per-project queues of pending jobs. When a job finished (in the simulation) it would get one or more jobs from that project's pending queue. The problem: this could cause "holes" in the scheduling of GPUs, and produce an erroneous nonzero shortfall for GPUs, leading to infinite work fetch. The solution: maintain a separate (per-resource, not per--project)queue of pending coprocessor jobs. When a coprocessor job finishes, start pending jobs from the queue for that resource. Another change: the simulator did strict reservation of coprocessors. If there are 2 instances of CUDA, and a 1-instance job is running in the simulation, it wouldn't start an additional 2-instance job. This also can cause erroneous nonzero shortfalls. So instead, schedule coprocessors like CPUs, i.e. saturate them. This can cause distorted completion time estimates, but it's better than infinite work fetch.
  • Manager: change terms for STD, LTD