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

[Gecko]

Gecko, я вижу у тебя посчитанные задания не сразу отправляются на сервер. Лучше создай себе cc_config.xml файл как написано тут

https://distributed.org.ua/forum/index.php?...indpost&p=60435

сделал, передернул клиент, пока висит не отправлено.
п.с. а это файл текстовый должен быть?

[Rilian]

Gecko, это должен быть .xml файл

если у тебя в Виндовсе не показывает расширения файлов - самое время настроить чтобы показывало

[Gecko]

Gecko, это должен быть .xml файл

если у тебя в Виндовсе не показывает расширения файлов - самое время настроить чтобы показывало

я не пользуюсь проводником, файловые менеджеры.
я почему спрашивал о формате, то есть его нужно создавать с помощю спец. или обычный текстовый файл с вышеупомянутыми внутреностями и расширением .xml ?
п.с. не проще выложить этот файл уже готовый? )

UPD: разобрался с файлом, но не отправляет все равно, висит по 10 заданий

[LSA]

<cc_config>
<log_flags>
<coproc_debug>1</coproc_debug>
<http_debug>1</http_debug>
<proxy_debug>1</proxy_debug>
</log_flags>
<options>
<allow_multiple_clients>1</allow_multiple_clients>
<http_1_0>1</http_1_0>
<ncpus>2</ncpus>
<report_results_immediately>1</report_results_immediately>
</options>
</cc_config>

Це мій cc_config.xml
цей файл попинен бути в папці Data directory.
Подивись уважно на свої картинки.

[x3mEn]

Тут багато зайвого або специфічного саме для тебе.
Достатньо буде такого cc_config.xml:

<cc_config>
  <options>
    <report_results_immediately>1</report_results_immediately>
  </options>
</cc_config>

[Gecko]

цей файл попинен бути в папці Data directory.

ну у меня нету такой папки в боинке.

[LSA]

C:\ProgramData\BOINC
На твоїй картинці в лозі боінка, синім по білому написано де знаходиться Data directory

[Gecko]

C:\ProgramData\BOINC
На твоїй картинці в лозі боінка, синім по білому написано де знаходиться Data directory

ОМГ спасибо! какой же я слепой, после слова програм игнорирую текст

[(_KoDAk_)]

BOINC 7.2.33 upgraded to recommended for all platforms.

Preliminary Change Log 7.2.30 --> 7.2.33:

(Show/Hide)

MGR: Disable downloading image files in notices.
LIB: Disable the ability to download images within notices.
client: Give a visual indication of a hot fix.
MGR: Disable downloading of all file types. POGS is also using a script to generate an image.
client and manager: the set_cc_config and get_cc_config GUI RPCs had nonstandard replies, which weren't parsed correctly by the calling code.

The reply from a GUI RPC that don't return info is one of:
<success/>
<error>error message</error>
<status>N</status>

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

Use these flags from the cc_config.xml file.

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

[Death]

наприклад 7 версія українізована

[(_KoDAk_)]

Preliminary Change Log 7.2.33 --> 7.2.34:
HZ

[Waterfall]

Preliminary Change Log 7.2.33 --> 7.2.34:
HZ

Look under the spoiler...

(Show/Hide)

Preliminary Change Log 7.2.33 --> 7.2.34:

client: fix bugs with CPU throttling and GPU apps.
Various bad things could happen when CPU throttling was used together w/ GPU apps.
Examples:
-> on a multi-GPU system, several GPU tasks are assigned to the same GPU.
-> a suspended GPU task remains in memory (tying up its GPU resources) while other tasks try to use the GPU.
The problem was that parts of the code assumed that suspended GPU processes don't exist - i.e. that when a GPU task is suspended it's always removed from memory.
This isn't true in the presence of CPU throttling.
So David made the following changes:
-> When assigning GPUs to tasks, treat suspended tasks like running tasks (i.e. reserve their GPUs).
-> At the end of the CPU-scheduling logic, if there are any GPU tasks that are suspended and not scheduled, remove them from memory, and trigger a reschedule so we can reallocate their GPUs.
Also, a cosmetic change: in the resource usage string shown in the GUI, include "(device X)" even if the task is suspended (i.e. because of throttling).
Also: zero out COPROC::opencl_device_indexes[] so we don't write a garbage number to init_data.xml for non-OpenCL jobs.

MGR: Store the ISO language ID for future use.
Usage: wxString strLang = wxGetApp().GetISOLanguageID();
MGR: Bug fix to my previous commit, initialize string after we initialize the wxLocale object with the proper locale information.
Client and Manager: make notices translatable

-> Add a GUI RPC ("set_language") that lets the Manager communicate the user's selected language code to the client at startup.
-> The client stores the language code in the client state file.
-> The client appends a "lang=X" GET argument to the URLs from which notices are fetched.
-> The next steps (not done) are 1) to change the get_notices.php script to parse the argument and do translation, and 2) extend our Pootle system to allow volunteer translation of notices by all projects.

[Waterfall]

Preliminary Change Log 7.2.34 --> 7.2.35

(Show/Hide)

MGR: work around a problem sizing the URL TextEdit field in the Attach Wizard Project Info page when a larger default font size is selected on Windows.
I don’t understand why this “fixes” it and I suspect there is a better solution.
MGR: Fix drawing of Task Control on Windows.

Preliminary Change Log 7.2.35 --> 7.2.36

(Show/Hide)

MGR: Prevent zero-size window in a rare situation where registry values have accidentally been set to zero.
MGR: Reverse commit a1fb470 (Fix drawing of Task Control on Windows) to fix build break; that change was for use with wxWidgets 3.0 only and should not have been ported to this branch.
client: Fix typo which had no actual effect in practice.
client: fix bug that caused idle GPUs when CPU throttling used.
client: if have a non-English language, set ACCEPT_LANGUAGE in all HTTP requests.
client: message tweak.
client: fix bugs involving CPU throttling and GPU apps.
Suspended tasks can be either left in memory (LIM) or removed from memory (RFM). CPU throttling always uses LIM. Other types of suspension (e.g. user request) use LIM or RFM depending on user prefs, except that RFM is always used for GPU tasks.
There was a bug: if tasks were suspended because of CPU throttling, and then the user suspended activity, GPU apps would remain LIM. They need to be RFM.
client: allow <file> in app_info.xml
In a checkin on 20 July 2011, I changed <file_info> to <file> in client_state.xml. However, the code that parses app_info.xml still requires <file_info>. This means you can't copy and paste stuff from client_state.xml to app_info.xml. Fix: parse either <file> or <file_info> in app_info.xml
client: when write file upload error XML to stderr, include user-friendly string.
client: report tasks within 1 hour of completion... instead of 24. Better user experience at the expense of slightly increased server load.

[Waterfall]

Preliminary Change Log 7.2.36 --> 7.2.37

(Show/Hide)

MGR: Remove outdated comments.
client: fix bug that caused lots of spurious "no shared memory segment" msgs.

ACTIVE_TASK_SET::suspend_all() originally skipped tasks in states other than PROCESS_EXECUTING. I took this out in commit 47b4d6b because - for example - a GPU task might be suspended due to CPU throttling, and therefore left in memory, but if it's then suspended for some other reason, it must be removed from memory.

However, this change was overkill - it causes tasks for which no process exists to be suspended, resulting in the spurious msgs.

Solution: skip tasks in states other than PROCESS_EXECUTING and PROCESS_SUSPENDED.

lib: make run_on_batteries false for all platforms by default.

[(_KoDAk_)]

Preliminary Change Log 7.2.37 --> 7.2.38:

(Show/Hide)

client: job scheduler tweaks to avoid idle CPUs
-> Allow overcommitment by > 1 CPU. E.g. If there are two 6-CPU jobs on an 8 CPU machine, run them both.
-> Prefer MT jobs to ST jobs in general. When reorder the run list (i.e. converting "preliminary" to "final" list), prefer job J1 to J2 if:
1) J1 is EDF and J2 isn't.
2) J1 uses GPUs and J2 doesn't.
3) J1 is in the middle of a timeslice and J2 isn't.
4) J1 uses more CPUs than J2.
5) J1's project has higher scheduling priority than J2's ... in that order.

4) is new; it replaces the function promote_multi_thread_jobs(), which did something similar but didn't work in some cases.

client: fix problems related to CPU throttling.
-> Don't throttle GPU apps. GPU apps spend all their time in a critical section, during which they can't be suspended. They length of these critical sections (i.e. of GPU kernels) may be a significant part of a second, or more, so sub-second throttling isn't possible.
-> Account elapsed time correctly when throttling is used.
-> Also (not related to throttling) don't schedule a job in QUIT_PENDING or ABORT_PENDING state. Doing so results in 2 processes in the slot dir, and can cause the job to fail.

client: Fix compiler warning (unused static function).
client: if app doesn't report fraction done, estimate it.
client: if app doesn't report fraction done, estimate fraction done in a way that converges to but never reaches 100%.