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

[Andrey Fenchenko]

Появилась новая седьмая ветка в развитии BOINC

Актуальная версия для загрузки: 7.4.*
recommended \ 7.4.*


Ссылки для прямой загрузки:

Поскольку они часто меняются, то в этом нет смысла. Ссылка на все версии ниже.

Все версии BOINC можно качать ОТСЮДА

Описание изменений: http://bolt.berkeley.edu/dev/forum_thread.php?id=6698 До 7.0.65

Описание изменений: http://bolt.berkeley.edu/dev/forum_thread.php?id=8378 С 7.1.1
===============================================

Use these flags from the cc_config.xml file.

===============================================

 

P.S. Отличий от шестой версии не нашел. Вкладку "Сообщения" так и не вернули.
P.P.S. По мере выхода новых версий ссылки в шапке будут обновляться.

Це повідомлення відредагував Death: Oct 31 2014, 22:40

[(_KoDAk_)]

Preliminary Change Log 7.1.17 --> 7.1.18:

(Show/Hide)

Mac installer:Add BOINC Installer icon to dialogs in the Postinstall app.
client: fix bug that allowed work fetch request while file uploads active

A while back we added a mechanism intended to defer work-request RPCs while file uploads are happening, with the goal of reporting completed tasks sooner and reducing the number of RPCs. There were 2 bugs in this mechanism.
- First, the decision of whether an upload is active was flawed; if several uploads were active and 1 finished, it would act like all had finished.
- Second, when WORK_FETCH::choose_project.cpp() picks a project, it sets p->sched_rpc_pending to RPC_REASON_NEED_WORK. If we then decide not to request work because an upload is active, we need to clear this field. Otherwise scheduler_rpc_poll() will do an RPC to it,
piggybacking a work request and bypassing the upload check.

client: fill in HOST_INFO producet_name field for Macintosh.

This returns an Apple hardware model designation such as "MacPro3,1". One source for converting this to a common model name is:
http://?http://www.everymac.com/systems/by_capability/mac-specs-by-machine-model-machine-id.html

client: fix bug that delayed work fetch from non-CPU-intensive projects.

We were waiting until there was no task for the project before asking for another task. We should have been waiting until there was no in-progress task.

client: fix bug that sometimes prevented work fetch when GPU exclusions used.
MGR: update progress display in simple view more frequently. Update progress display if progress has changed by at least 0.001% (was 0.1%).
MGR: if max_ncpus_pct is 0, show 100% in Advanced Preferences dialog.
client: remove code that avoids overcommitting CPUs if MT jobs present.

This can lead to starving the CPUs if there are both GPU and MT jobs. The basic problem is that a host with GPUs will never have all its CPUs available for MT jobs. It should probably advertise fewer CPUs, or something.

MGR: if max_ncpus_pct is 0, show 100% in Advanced Preferences dialog.
client: Win version name tweaks, from [P3D} Crashtest.
client: clear max_concurrent if app_config.xml no longer exists. If you had an app_config.xml that limited the # of concurrent tasks for an app, and you delete it and do "reread config", then remove the limit.
MGR: test if (max_ncpus_pct == 0) instead of (max_ncpus_pct < 0.1) in Advanced Preferences dialog (requested by David Anderson).
client: if project sends dont_use_dcf, set its DCF to 1.
Mac uninstaller: localize the dialog strings in the Uninstall BOINC app.
Mac uninstaller: fix comments.
Mac installer and uninstaller: eliminate minor memory leaks.
Mac installer: eliminate minor memory leaks.
LOC: Update template for latest changes.
LOC: Update translation files.
LOC: Fix bug reported when using Italian on Debian.
boinccmd: show result states as strings instead of numbers.

Not really a bug, but a small warning for alpha testers who update to 7.1.18

I think due to http://boinc.berkeley.edu/trac/changeset/3...bf5267/boinc-v2
(MGR: if max_ncpus_pct is 0, show 100% in Advanced Preferences dialog.), the amount of CPUs used by BOINC gets reset to 100%.

This means that people who have set up BOINC to run with all but one or more CPU cores from local advanced preferences --e.g. to accommodate GPUs-- that they'll have to reset this preference back to the value they had before upgrading!

So keep an eye out, don't just install and walk away.