How to run multiple GPUs from BOINC

Message boards : Questions and problems : How to run multiple GPUs from BOINC
Message board moderation

To post messages, you must log in.

AuthorMessage
Sandman192

Send message
Joined: 28 Aug 19
Posts: 49
United States
Message 99907 - Posted: 12 Jul 2020, 18:09:04 UTC

I added a second GPU and can't get it to run both.
7/12/2020 12:39:51 PM | | CUDA: NVIDIA GPU 1 (not used): GeForce GTX 980 (driver version 451.48, CUDA version 11.0, compute capability 5.2, 4096MB, 3378MB available, 4979 GFLOPS peak)
7/12/2020 12:39:51 PM | | OpenCL: NVIDIA GPU 1 (ignored by config): GeForce GTX 980 (driver version 451.48, device version OpenCL 1.2 CUDA, 4096MB, 3378MB available, 4979 GFLOPS peak)

Plus, why isn't multiple GPUs on by default? And I wish the setting where in the BOINC client.
ID: 99907 · Report as offensive
Sandman192

Send message
Joined: 28 Aug 19
Posts: 49
United States
Message 99911 - Posted: 13 Jul 2020, 0:54:49 UTC - in response to Message 99907.  

Upgrading or doing a fresh install of BOINC v7.16.7 will delete or not creat a cc_config.xml. I see this as a major bug in this.

I search long and hard to get my computer to run more than 1 GPU on my computer. For one it's off by default, it should be in 'Computing preference' and cc_config.xml is not there anymore. It doesn't have to be this hard to get BOINC to configure to use more than one GPU.
It should be in the 'Computing preference' option to set it and not off by default.

If anyone has this problem with a new version of BOINC v7.16.7 for mutable GPUS than just add a cc_config.XML. I didn't know how to create an .XML so I copied any .XML file I found and pasted it back in the same directory and now I have 2 of the same file with one having copy added to the file. I right-clicked on the file and clicked 'edit' and 'select all' and pasted the command down below. Then I closed and saved the file. And all you have to do is rename the file with copy in it to 'cc_config and restart BOINC.
<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>
ID: 99911 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 99919 - Posted: 13 Jul 2020, 7:38:13 UTC - in response to Message 99911.  

Upgrading or doing a fresh install of BOINC v7.16.7 will delete or not creat a cc_config.xml. I see this as a major bug in this.
Upgrading BOINC does not delete anything in the data directory, where cc_config.xml resides.
However, BOINC does not start with a default cc_config.xml file, you will always have to make one. Either by hand, or easily have a fully populated one by editing the Event Log options... menu in BOINC Manager (advanced view).

For one it's off by default, it should be in 'Computing preference' and cc_config.xml is not there anymore.
As explained, BOINC does by default not come with cc_config.xml; if you never had it it wasn't removed, you just never had it.

It should be in the 'Computing preference' option to set it and not off by default.
Tell the developers over at BOINC Github (When the Github server is back at least, never seen it down...)
ID: 99919 · Report as offensive
Sandman192

Send message
Joined: 28 Aug 19
Posts: 49
United States
Message 99938 - Posted: 14 Jul 2020, 9:45:19 UTC - in response to Message 99919.  

Upgrading BOINC does not delete anything in the data directory, where cc_config.xml resides.

No, I'm just making things up! It did because I have seen in the BOINC logs that cc_config.xml is missing. Which I've never seen for years.
However, BOINC does not start with a default cc_config.xml file, you will always have to make one.
As explained, BOINC does by default not come with cc_config.xml; if you never had it it wasn't removed, you just never had it.

Plus, It didn't create a cc_config.xml ether. I know it's not that way in older versions.
So you don't know what you're talking about. I've seen it. I've been a BOINC user for over 8 years. Looking through logs and BOINC folders.

And your help desk and tester??? How do you think I know about cc_config.xml? It wasn't from Google.
ID: 99938 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 99939 - Posted: 14 Jul 2020, 11:08:10 UTC - in response to Message 99938.  

Our knowledge of cc_config.xml comes from three places:

The User Manual
Detailled knowledge of the source code
Experience (15 years, in my case) of running BOINC.

cc_config.xml is an optional file. From the user manual, "If the file is absent, the default configuration is used." The BOINC installers for Windows and Linux do not create it. I cannot speak from experience of Mac OS X. 'Skinned' installers for other versions of BOINC (WCG, CharityEngine) may include it, but that's beyond our scope here.

As Jord says, uninstalling BOINC (whether manually, or as an automated part of the upgrade procedure) does not delete any user data. cc_config.xml is user data.

It is possible that a new installation of BOINC may create different file locations for programs and data than the ones you previously used. This would have been displayed during installation, but not everybody checks. Normally, the previous locations are remembered and reused.
ID: 99939 · Report as offensive
robsmith
Volunteer tester
Help desk expert

Send message
Joined: 25 May 09
Posts: 1283
United Kingdom
Message 99940 - Posted: 14 Jul 2020, 11:08:25 UTC

During startup BOINC checks to see if there is a cc_config.xml file present, if there isn't one, then it reports it's absence, if it is there it uses it. You should read that rather terse message as "Since there isn't a cc_config.xml file BOINC is going to us the default settings" - a simple "this is why BOINC is doing it this way", nothing more, nothing less.
BOINC does not, and as far as I'm aware, never has auto-generated a cc_config.xml file, so the fact that you have been seeing this message for a very long time is only confirming the default situation and not telling you there is an error with your system.

If you really feel that the file should be auto-generated then you have to engage in dialogue with the developers, using GtHub, using the link provided by Jord rather than ranting at Jord.
ID: 99940 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 99941 - Posted: 14 Jul 2020, 12:36:23 UTC
Last modified: 14 Jul 2020, 12:49:25 UTC

Thank the deities, I don't know what I'm talking about re: BOINC. The curse has been broken, I can finally leave here!
And stop writing the documentation for it, stop putting bugs into their bug system, stop helping people who really don't know B from OINC. I'm free, I'm free!
ID: 99941 · Report as offensive
Sandman192

Send message
Joined: 28 Aug 19
Posts: 49
United States
Message 99968 - Posted: 15 Jul 2020, 8:09:36 UTC
Last modified: 15 Jul 2020, 8:12:19 UTC

cc_config.xml is an optional file.

BOINC does not, and as far as I'm aware, never has auto-generated a cc_config.xml file

No, it is not. It's been there from the start. I remember the cc_config.xml codes in there that took at least 3 pages of coding. And no cc_config.xml never ones showed up in "Event log" that the cc_config.xml was missing.

I certainly didn't type or copy and paste all that stuff in. Why would I? I had no need to.
ID: 99968 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 99970 - Posted: 15 Jul 2020, 9:18:59 UTC - in response to Message 99968.  

No, it is not. It's been there from the start. I remember the cc_config.xml codes in there that took at least 3 pages of coding. And no cc_config.xml never ones showed up in "Event log" that the cc_config.xml was missing.

I certainly didn't type or copy and paste all that stuff in. Why would I? I had no need to.
Can you give us an indication of when that anecdote relates to?

Originally, (2005 or thereabouts) BOINC had no way of auto-creating cc_config.xml

Round about 2015 (ten years later - subject to checking) and version 7.4, a dialog was added allowing users to change their Event Log settings visually, rather than creating/editing the file manually. Usage of the 'Event log options' dialog re-writes the entire cc_config.xml file, and thereby creates a new default file if none existed before. This is the first and only situation where BOINC creates the file - and it happens during usage of BOINC Manager, not at installation.
ID: 99970 · Report as offensive
Sandman192

Send message
Joined: 28 Aug 19
Posts: 49
United States
Message 99971 - Posted: 15 Jul 2020, 9:27:36 UTC
Last modified: 15 Jul 2020, 9:36:42 UTC

Ok, I installed Windows 10 on to a Vbox and installed BOINC 7.8.0.

No cc_config.xml

Now I know how it got there.

But I do know it was pages long.

And I do know now that I remember it saying that every time I check the logs...
7/15/2020 3:58:01 AM | | cc_config.xml not found - using defaults

But I did have the file before and for some reason, it is gone after upgrading BOINC to 7.16.7.

The point is that I figure it out and got it to run all GPUS.
Which why it's not on by default for a program that runs CPU and GPUS and has no option to change it in the client settings is be on me.

I see now and thanks.
ID: 99971 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 99972 - Posted: 15 Jul 2020, 9:37:45 UTC - in response to Message 99970.  
Last modified: 15 Jul 2020, 10:13:17 UTC

This is the first and only situation where BOINC creates the file - and it happens during usage of BOINC Manager, not at installation.
Using the Exclusive Applications menu option would already write a fully populated cc_config.xml file way before the Event Log options menu came in.
ID: 99972 · Report as offensive
Sandman192

Send message
Joined: 28 Aug 19
Posts: 49
United States
Message 99973 - Posted: 15 Jul 2020, 9:50:56 UTC - in response to Message 99971.  

This is what I'm talking about... So BOINC does creat cc_config.xml in a matter of speaking. But is the new version of BOINC v7.16.7 deleting this file??? If any one out there has the cc_config file and find out it's missing then you need to report as a bug on this.
<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<android_debug>1</android_debug>
<app_msg_receive>1</app_msg_receive>
<app_msg_send>1</app_msg_send>
<async_file_debug>1</async_file_debug>
<benchmark_debug>1</benchmark_debug>
<checkpoint_debug>1</checkpoint_debug>
<coproc_debug>1</coproc_debug>
<cpu_sched>1</cpu_sched>
<cpu_sched_debug>1</cpu_sched_debug>
<cpu_sched_status>1</cpu_sched_status>
<dcf_debug>1</dcf_debug>
<disk_usage_debug>1</disk_usage_debug>
<file_xfer_debug>1</file_xfer_debug>
<gui_rpc_debug>1</gui_rpc_debug>
<heartbeat_debug>1</heartbeat_debug>
<http_debug>1</http_debug>
<http_xfer_debug>1</http_xfer_debug>
<idle_detection_debug>1</idle_detection_debug>
<mem_usage_debug>1</mem_usage_debug>
<network_status_debug>1</network_status_debug>
<notice_debug>1</notice_debug>
<poll_debug>1</poll_debug>
<priority_debug>1</priority_debug>
<proxy_debug>1</proxy_debug>
<rr_simulation>1</rr_simulation>
<rrsim_detail>1</rrsim_detail>
<sched_op_debug>1</sched_op_debug>
<scrsave_debug>1</scrsave_debug>
<slot_debug>1</slot_debug>
<state_debug>1</state_debug>
<statefile_debug>1</statefile_debug>
<suspend_debug>1</suspend_debug>
<task_debug>1</task_debug>
<time_debug>1</time_debug>
<trickle_debug>1</trickle_debug>
<unparsed_xml>1</unparsed_xml>
<work_fetch_debug>1</work_fetch_debug>
</log_flags>
<options>
<abort_jobs_on_exit>0</abort_jobs_on_exit>
<allow_multiple_clients>0</allow_multiple_clients>
<allow_remote_gui_rpc>0</allow_remote_gui_rpc>
<client_version_check_url>https://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
<client_new_version_text></client_new_version_text>
<client_download_url>https://boinc.berkeley.edu/download.php</client_download_url>
<disallow_attach>0</disallow_attach>
<dont_check_file_sizes>0</dont_check_file_sizes>
<dont_contact_ref_site>0</dont_contact_ref_site>
<lower_client_priority>0</lower_client_priority>
<dont_suspend_nci>0</dont_suspend_nci>
<dont_use_vbox>0</dont_use_vbox>
<exit_after_finish>0</exit_after_finish>
<exit_before_start>0</exit_before_start>
<exit_when_idle>0</exit_when_idle>
<fetch_minimal_work>0</fetch_minimal_work>
<fetch_on_update>0</fetch_on_update>
<force_auth>default</force_auth>
<http_1_0>0</http_1_0>
<http_transfer_timeout>300</http_transfer_timeout>
<http_transfer_timeout_bps>10</http_transfer_timeout_bps>
<max_event_log_lines>2000</max_event_log_lines>
<max_file_xfers>8</max_file_xfers>
<max_file_xfers_per_project>2</max_file_xfers_per_project>
<max_stderr_file_size>0</max_stderr_file_size>
<max_stdout_file_size>0</max_stdout_file_size>
<max_tasks_reported>0</max_tasks_reported>
<ncpus>-1</ncpus>
<network_test_url>https://www.google.com/</network_test_url>
<no_alt_platform>0</no_alt_platform>
<no_gpus>0</no_gpus>
<no_info_fetch>0</no_info_fetch>
<no_opencl>0</no_opencl>
<no_priority_change>0</no_priority_change>
<os_random_only>0</os_random_only>
<process_priority>-1</process_priority>
<process_priority_special>-1</process_priority_special>
<proxy_info>
<socks_server_name></socks_server_name>
<socks_server_port>80</socks_server_port>
<http_server_name></http_server_name>
<http_server_port>80</http_server_port>
<socks5_user_name></socks5_user_name>
<socks5_user_passwd></socks5_user_passwd>
<socks5_remote_dns>0</socks5_remote_dns>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
<no_autodetect>0</no_autodetect>
</proxy_info>
<rec_half_life_days>10.000000</rec_half_life_days>
<report_results_immediately>0</report_results_immediately>
<run_apps_manually>0</run_apps_manually>
<save_stats_days>30</save_stats_days>
<skip_cpu_benchmarks>0</skip_cpu_benchmarks>
<simple_gui_only>0</simple_gui_only>
<start_delay>0.000000</start_delay>
<stderr_head>0</stderr_head>
<suppress_net_info>0</suppress_net_info>
<unsigned_apps_ok>0</unsigned_apps_ok>
<use_all_gpus>0</use_all_gpus>
<use_certs>0</use_certs>
<use_certs_only>0</use_certs_only>
<vbox_window>0</vbox_window>
</options>
</cc_config>
ID: 99973 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 99974 - Posted: 15 Jul 2020, 10:21:53 UTC - in response to Message 99973.  
Last modified: 15 Jul 2020, 10:22:37 UTC

BOINC will certainly not make a cc_config.xml file with all the debug options on by default. Only <task>, <sched_ops> and <file_xfer> are on by default. I wouldn't use that cc_config.xml file as this will give a lot of information about the running of BOINC, most of it being totally useless to the normal user. It may even completely hang the client because of the overkill on information.

The old cc_config.xml (cc stands for client configuration) was intended to set the debug flags for testing the BOINC client and project applications. Over time other options were added. Because one can hang the client when adding too many (or all) log_flags, the making of and using of cc_config.xml is for advanced users (and alpha testers) only. Hence also why it will only be populated from the Advanced view of BOINC Manager, not from Simple View.
ID: 99974 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 99975 - Posted: 15 Jul 2020, 10:29:17 UTC - in response to Message 99973.  

This is what I'm talking about... So BOINC does creat cc_config.xml in a matter of speaking. But is the new version of BOINC v7.16.7 deleting this file??? If any one out there has the cc_config file and find out it's missing then you need to report as a bug on this.
That's a fair question, but in my experience, the answer is 'NO'.

I have two laptops on the desk in front of me - one Windows 7, the other Windows 10. They are both running v7.16.7. They both have a cc_config.xml file, and they both have a copy of the v7.16.7 downloadable installer file. That file was first made available on 31 May 2020.

The Windows 7 machine downloaded the installer at 11:24 om 01 June 2020. It's cc_config.xml file is datestamped at 16:24 on 9 March 2019. So, no delete/recreate there.

The Windows 10 machine downloaded the installer at 09:49 on 12 June 2020. It's cc_config.xml file is datestamped at 10:23 on 12 June 2020. A delete/recreate event is possible in that case, but unconfirmed. I think I would have noticed and remembered it. The restart log file on that machine records the version change (7.16.5 -> 7.16.7) at 09:52, and continues to load my normal cc_config.xml settings. So, no deletion.

I was closely involved in the events of 30 May - 01 June that led to the creation and release of v7.16.7. The only significant change (and the reason for the release) was https://github.com/BOINC/boinc/commit/ee17a911a43d54613363a776e1c65a59e8b8fd2b. That change did not affect cc_config.xml in any way.
ID: 99975 · Report as offensive

Message boards : Questions and problems : How to run multiple GPUs from BOINC

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.