Boinc-client Version 6.x.x, Обсуждение работы шестой версии клиента Налаштування

[(_KoDAk_)]

ПОЛНАЯ история изменений версий BOINC с датами выхода релизов

Change Log для 6.11.хх

BOINC (6 - 6.10.58) Versions Change Log

BOINC 6.7/6.8/GR6.8 Change Log

Все версии боинка для закачки

ВСЕ ВЕРСИИ С 5-й по 6-ю <- РЕКОМЕНДУЕТСЯ КАЧАТЬ ОТСЮДА.

все версии, включая самые последние девелоперские!

официальный форум разработчиков (зарегистрироваться)

[(_KoDAk_)]

Tag for 6.10.5 release, all platforms boinc_core_release_6_10_5
- Mgr: skip exit confirmation dialog if user pressed emergency Exit button on AsyncRPCDlg
- Mac installer: ask user whether to allow non-administrative users to run and control BOINC
- Mac installer: create a new command-line tool AddRemoveUser; updated ReadMe file

- client: add code for faking ATI GPUs
- client: cap time_stats dt at 2 weeks, so people upgrading to 6.10 won't get big drop in on_frac.
- client: fix bug in RR simulation: 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.
- client: save space in req msg. Didn't make much difference.
- client: fix bug in FIFO selection of coproc jobs (Comment by David: senility setting in?)
- client: add <fraction_done> to boinc_task_state.xml
- client: change order in poll loop so that:
1) job finishes
2) job gets marked as "ready to report"
3) scheduler RPC is initiated
Hopefully this won't have an unintended side-effect.

- client: tweak policy for device busy time. Should eliminate some spurious "job won't complete by deadline" msgs.
- client: cap project-supplied backoffs at 28 days
- client: anal-retentive alphabetization
- client and scheduler RPC: add optional <cpu_backoff>, <cuda_backoff>, 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.