Different apps for different GPUs
I have a gtx 560 and hd 4000. I like solo collatz on the 560 but I would like to run a shorter WU than the solo one on the hd4000. Can someone share a method for getting different WUs per device per host? I would guess this is either done in app_info or app_config?
Re: Different apps for different GPUs
Quote:
Originally Posted by
MindCrime
I have a gtx 560 and hd 4000. I like solo collatz on the 560 but I would like to run a shorter WU than the solo one on the hd4000. Can someone share a method for getting different WUs per device per host? I would guess this is either done in app_info or app_config?
I will give you an in-artful approach and hopefully someone will come along with an elegant solution.
I assume the GPUs are on different machines.
1. Set your collatz webpage preferences to the size of WU you want for the 1st machine.
2. Set your 1st machine to receive 10 days of collatz. Once downloaded, set it to no new tasks.
3. Set the collatz webpage preferences to the size of WU you want for the 2nd machine.
4. Set the 2nd machine to receive 10 days of collatz. Once downloaded, set it to no new tasks.
Re: Different apps for different GPUs
They are in the same machine, hd 4000 on the CPU die and the gtx 560 via PCIe.. so location preferences wouldn't help.
Re: Different apps for different GPUs
I would think that would be done in the cc_cong.xml using <exclude_gpu> and specifying the app also.
Re: Different apps for different GPUs
Something like this in cc_config.xml:
<exclude_gpu>
<url>http://boinc.thesonntags.com/collatz/</url>
<type>nvidia</type>
<app>mini_collatz</app>
</exclude_gpu>
<exclude_gpu>
<url>http://boinc.thesonntags.com/collatz/</url>
<type>intel_gpu</type>
<app>solo_collatz</app>
</exclude_gpu>
Re: Different apps for different GPUs
Re: Different apps for different GPUs
Re: Different apps for different GPUs
Where in the cc_config.xml should i put that?
<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<android_debug>0</android_debug>
<app_msg_receive>0</app_msg_receive>
<app_msg_send>0</app_msg_send>
<async_file_debug>0</async_file_debug>
<benchmark_debug>0</benchmark_debug>
<checkpoint_debug>0</checkpoint_debug>
<coproc_debug>0</coproc_debug>
<cpu_sched>0</cpu_sched>
<cpu_sched_debug>0</cpu_sched_debug>
<cpu_sched_status>0</cpu_sched_status>
<dcf_debug>0</dcf_debug>
<disk_usage_debug>0</disk_usage_debug>
<file_xfer_debug>0</file_xfer_debug>
<gui_rpc_debug>0</gui_rpc_debug>
<heartbeat_debug>0</heartbeat_debug>
<http_debug>0</http_debug>
<http_xfer_debug>0</http_xfer_debug>
<mem_usage_debug>0</mem_usage_debug>
<network_status_debug>0</network_status_debug>
<notice_debug>0</notice_debug>
<poll_debug>0</poll_debug>
<priority_debug>0</priority_debug>
<proxy_debug>0</proxy_debug>
<rr_simulation>0</rr_simulation>
<rrsim_detail>0</rrsim_detail>
<sched_op_debug>0</sched_op_debug>
<scrsave_debug>0</scrsave_debug>
<slot_debug>0</slot_debug>
<state_debug>0</state_debug>
<statefile_debug>0</statefile_debug>
<suspend_debug>0</suspend_debug>
<task_debug>0</task_debug>
<time_debug>0</time_debug>
<trickle_debug>0</trickle_debug>
<unparsed_xml>0</unparsed_xml>
<work_fetch_debug>0</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>http://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
<client_new_version_text></client_new_version_text>
<client_download_url>http://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>
<exclusive_app>vlc.exe</exclusive_app>
<exclusive_gpu_app>vlc.exe</exclusive_gpu_app>
<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>http://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_priority_change>0</no_priority_change>
<os_random_only>0</os_random_only>
<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>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
</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</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>
Re: Different apps for different GPUs
"A GPU exclusion in your cc_config.xml file refers to an unknown application 'mini_collatz'. Known applications: 'solo_collatz', 'large_collatz'"
is what I get after i pasted it within the options flags
A GPU exclusion in your cc_config.xml file refers to an unknown application 'mini_collatz'. Known applications: 'solo_collatz', 'large_collatz'
is this a server side thing, did i configure it wrong, do i need to manually download the other applications? Actually I just did that, downloaded the following to the collatz application directory
mini_collatz_6.04_windows_x86_64__opencl_intel_gpu .exe
mini_collatz_6.04_windows_x86_64__opencl_intel_gpu .pdb
mini_collatz_6.04_windows_x86_64__opencl_intel_gpu .config
Re: Different apps for different GPUs
Quote:
Originally Posted by
MindCrime
"A GPU exclusion in your cc_config.xml file refers to an unknown application 'mini_collatz'. Known applications: 'solo_collatz', 'large_collatz'"
is what I get after i pasted it within the options flags
check the project folder for mini_collatz. If it's not there, you will have to get it.......anyone have the manual download link?? I just did the hokey pokey with the options after they became available. I never did get to the micro. ;)
Re: Different apps for different GPUs
Quote:
Originally Posted by
MindCrime
Where in the cc_config.xml should i put that?
<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<android_debug>0</android_debug>
<app_msg_receive>0</app_msg_receive>
<app_msg_send>0</app_msg_send>
<async_file_debug>0</async_file_debug>
<benchmark_debug>0</benchmark_debug>
<checkpoint_debug>0</checkpoint_debug>
<coproc_debug>0</coproc_debug>
<cpu_sched>0</cpu_sched>
<cpu_sched_debug>0</cpu_sched_debug>
<cpu_sched_status>0</cpu_sched_status>
<dcf_debug>0</dcf_debug>
<disk_usage_debug>0</disk_usage_debug>
<file_xfer_debug>0</file_xfer_debug>
<gui_rpc_debug>0</gui_rpc_debug>
<heartbeat_debug>0</heartbeat_debug>
<http_debug>0</http_debug>
<http_xfer_debug>0</http_xfer_debug>
<mem_usage_debug>0</mem_usage_debug>
<network_status_debug>0</network_status_debug>
<notice_debug>0</notice_debug>
<poll_debug>0</poll_debug>
<priority_debug>0</priority_debug>
<proxy_debug>0</proxy_debug>
<rr_simulation>0</rr_simulation>
<rrsim_detail>0</rrsim_detail>
<sched_op_debug>0</sched_op_debug>
<scrsave_debug>0</scrsave_debug>
<slot_debug>0</slot_debug>
<state_debug>0</state_debug>
<statefile_debug>0</statefile_debug>
<suspend_debug>0</suspend_debug>
<task_debug>0</task_debug>
<time_debug>0</time_debug>
<trickle_debug>0</trickle_debug>
<unparsed_xml>0</unparsed_xml>
<work_fetch_debug>0</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>http://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
<client_new_version_text></client_new_version_text>
<client_download_url>http://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>
<exclusive_app>vlc.exe</exclusive_app>
<exclusive_gpu_app>vlc.exe</exclusive_gpu_app>
<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>http://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_priority_change>0</no_priority_change>
<os_random_only>0</os_random_only>
<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>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
</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</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>
Is bigger than my testament.:-o
Re: Different apps for different GPUs
Quote:
Originally Posted by
MindCrime
"A GPU exclusion in your cc_config.xml file refers to an unknown application 'mini_collatz'. Known applications: 'solo_collatz', 'large_collatz'"
is what I get after i pasted it within the options flags
A GPU exclusion in your cc_config.xml file refers to an unknown application 'mini_collatz'. Known applications: 'solo_collatz', 'large_collatz'
is this a server side thing, did i configure it wrong, do i need to manually download the other applications? Actually I just did that, downloaded the following to the collatz application directory
Your cc_config is quite a read! Within the Options tag is correct, now make sure Mini Collatz is selected in your project settings along with the applicable Plan Classes http://boinc.thesonntags.com/collatz...subset=project
The apps will download on their own when you get work. If they don't, you may try a project reset.
Re: Different apps for different GPUs
I have no idea why my cc_config is like that...i've never edited directly. What should it look like?
Well if it's placed in the cc_config correctly and i have mini selected in preferences and i've also manually downloaded the apps, just wondering why im getting the notice and why only solo and large are listed, not mini and micro as well.
Re: Different apps for different GPUs
Old thread, but I'll restart it. My problem is a little different. I have one computer that has 1-nv gpu and 3-ati gpus. If I set preferences to accept both types of work I get NV only. The only way I get any ATI work is too load up on nv, then turn it off in the preferences. As the nv work completes I get ATI to replace it. When I get to 150 ATI wus and 50 nv wus I turn both back on in the preferences and the nv only start coming in again. Repeat... Surely there is a better solution than having to babysit this computer. Ideas? Anyone?
Re: Different apps for different GPUs
Quote:
Originally Posted by
Sphynx
Old thread, but I'll restart it. My problem is a little different. I have one computer that has 1-nv gpu and 3-ati gpus. If I set preferences to accept both types of work I get NV only. The only way I get any ATI work is too load up on nv, then turn it off in the preferences. As the nv work completes I get ATI to replace it. When I get to 150 ATI wus and 50 nv wus I turn both back on in the preferences and the nv only start coming in again. Repeat... Surely there is a better solution than having to babysit this computer. Ideas? Anyone?
Can you post some lines from your event log? What version of BOINC are you using? Might tell of if it's a BOINC issue or a Collatz issue. I haven't run mixed NV/AMD in a while, but I remember getting work for both without a problem.
Re: Different apps for different GPUs
I can later this evening.
Re: Different apps for different GPUs
Quote:
Originally Posted by
Sphynx
I can later this evening.
not sure on syntax but ... <useallgpus> seems like a flag somewhere
Re: Different apps for different GPUs
Back in the old days when I ran GPUs that was always a problem in mixed systems when running the same project. Back then the only solution was what you are doing. I found it easier to run 2 different project with the GPUs so that I didn't have to babysit the computers.
Things may have changed ... then again they may be the same. I believe the problem was with the BOINC scheduler not asking for the correct type of WU.
Re: Different apps for different GPUs
Quote:
Originally Posted by
Bryan
Back in the old days when I ran GPUs that was always a problem in mixed systems when running the same project. Back then the only solution was what you are doing. I found it easier to run 2 different project with the GPUs so that I didn't have to babysit the computers.
Things may have changed ... then again they may be the same. I believe the problem was with the BOINC scheduler not asking for the correct type of WU.
Well, I still have this problem, but it will soon be resolved. I have only 25 million to go (about 5 days) to reach my billion on Collatz and at that point, I'm done...problem solved. :cool: Unfortunately there is no badge upgrade for 1 billion (WTF Slicker :p )and I'd need to add another billion (2 billion) to upgrade. Not sure I'd live that long with my hardware.