Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 15
Posts: 15   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1447 times and has 14 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
WCG ignoring device manager.

I have a machine on this project which is ignoring the settings that I have set in its device manager profile. It it a high end current gen rig with 4 GPU's running windows 8.1 and the latest x64 boinc install. The issue I have is that in device manager I have it set to only use 50% or 2 cores: "
On multiprocessors, at most use: 2 processors
On multiprocessors, use: 50.0% of processors"

For some reason the boinc client is completely ignoring this and this and is using all 4 cores. This is leading to my GPU projects (x2 ATI projects, x1 nvidia Project and x1 intel_gpu project) being starved completely and put into a waiting to run state. My question is why is the client ignoring the WCG pref's I have set?
[Sep 2, 2014 5:24:30 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

Additional question: Why does the intel 4600 GPU get underclocked when I have WCG tasks running?
[Sep 2, 2014 5:26:18 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

Have you clicked on Save after making the 50% / 2 cores settings?

Is the device in question assigned to the profile name in which you've made the settings?

If you're still stuck, the usual advice here is to reboot the machine and then paste here the first 50 or so lines from the BOINC Manager Event Log (Ctrl-Shift-E) in BOINC Manager; the number of lines may need to increase if you're running multiple BOINC projects in order to include all the start-up lines.

Can't help with the GPU question, sorry.
[Sep 2, 2014 5:37:56 PM]   Link   Report threatening or abusive post: please login first  Go to top 
branjo
Master Cruncher
Slovakia
Joined: Jun 29, 2012
Post Count: 1892
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

Hi Aedazan,

You have to set it in BOINC Manager / Preferences, otherwise it (Device manager setting) is overridden by such (BOINC Manager) settings.

Cheers peace
----------------------------------------

Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006

----------------------------------------
[Edit 1 times, last edit by branjo at Sep 2, 2014 5:38:55 PM]
[Sep 2, 2014 5:37:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

Ah, so what you are essentially saying is that I cannot limit boinc CPU usage by project. I would really like WCG to use only 2 cores and allow the other 2 cores to run the 4 GPU tasks.
[Sep 2, 2014 5:43:24 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

Yes, I clicked save ;)
Here is the dump that the log puts out:

3/09/2014 3:44:28 AM | | Starting BOINC client version 7.2.42 for windows_x86_64
3/09/2014 3:44:28 AM | | log flags: file_xfer, sched_ops, task
3/09/2014 3:44:28 AM | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
3/09/2014 3:44:28 AM | | Data directory: C:\ProgramData\BOINC
3/09/2014 3:44:28 AM | | Running under account Nick
3/09/2014 3:44:28 AM | | CUDA: NVIDIA GPU 0: GeForce GTS 450 (driver version 340.52, CUDA version 6.5, compute capability 2.1, 1024MB, 956MB available, 601 GFLOPS peak)
3/09/2014 3:44:28 AM | | CAL: ATI GPU 0: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (CAL version 1.4.1848, 1024MB, 991MB available, 4646 GFLOPS peak)
3/09/2014 3:44:28 AM | | CAL: ATI GPU 1: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (CAL version 1.4.1848, 1024MB, 991MB available, 4646 GFLOPS peak)
3/09/2014 3:44:28 AM | | OpenCL: NVIDIA GPU 0: GeForce GTS 450 (driver version 340.52, device version OpenCL 1.1 CUDA, 1024MB, 956MB available, 601 GFLOPS peak)
3/09/2014 3:44:28 AM | | OpenCL: AMD/ATI GPU 0: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (driver version 1445.5 (VM), device version OpenCL 1.2 AMD-APP (1445.5), 1024MB, 991MB available, 4646 GFLOPS peak)
3/09/2014 3:44:28 AM | | OpenCL: AMD/ATI GPU 1: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (driver version 1445.5 (VM), device version OpenCL 1.2 AMD-APP (1445.5), 1024MB, 991MB available, 4646 GFLOPS peak)
3/09/2014 3:44:28 AM | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version 10.18.10.3621, device version OpenCL 1.2, 1400MB, 1400MB available, 176 GFLOPS peak)
3/09/2014 3:44:28 AM | | OpenCL CPU: Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1445.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1445.5))
3/09/2014 3:44:28 AM | | OpenCL CPU: Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 3.0.1.10878, device version OpenCL 1.2 (Build 76413))
3/09/2014 3:44:28 AM | | Host name: Carbon
3/09/2014 3:44:28 AM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz [Family 6 Model 60 Stepping 3]
3/09/2014 3:44:28 AM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes syscall nx lm vmx tm2 pbe
3/09/2014 3:44:28 AM | | OS: Microsoft Windows 8.1: Core x64 Edition, (06.03.9600.00)
3/09/2014 3:44:28 AM | | Memory: 15.89 GB physical, 31.89 GB virtual
3/09/2014 3:44:28 AM | | Disk: 232.54 GB total, 157.82 GB free
3/09/2014 3:44:28 AM | | Local time is UTC +10 hours
3/09/2014 3:44:28 AM | | Config: use all coprocessors
3/09/2014 3:44:28 AM | | Config: don't compute while ExeFile.exe is running
3/09/2014 3:44:28 AM | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 11629441; resource share 3000
3/09/2014 3:44:28 AM | Milkyway@Home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 585984; resource share 10000
3/09/2014 3:44:28 AM | GPUGRID | URL http://www.gpugrid.net/; Computer ID 180843; resource share 999999
3/09/2014 3:44:28 AM | World Community Grid | URL http://www.worldcommunitygrid.org/; Computer ID 3140341; resource share 5
3/09/2014 3:44:28 AM | World Community Grid | General prefs: from World Community Grid (last modified 15-Aug-2014 01:58:46)
3/09/2014 3:44:28 AM | World Community Grid | Computer location: school
3/09/2014 3:44:28 AM | | General prefs: using separate prefs for school
3/09/2014 3:44:28 AM | | Reading preferences override file
3/09/2014 3:44:28 AM | | Preferences:
3/09/2014 3:44:28 AM | | max memory usage when active: 16272.03MB
3/09/2014 3:44:28 AM | | max memory usage when idle: 16272.03MB
3/09/2014 3:44:28 AM | | max disk usage: 80.00GB
3/09/2014 3:44:28 AM | | suspend work if non-BOINC CPU load exceeds 25%
3/09/2014 3:44:28 AM | | max upload rate: 5120 bytes/sec
3/09/2014 3:44:28 AM | | (to change preferences, visit a project web site or select Preferences in the Manager)
3/09/2014 3:44:28 AM | | Not using a proxy
3/09/2014 3:44:30 AM | Milkyway@Home | Sending scheduler request: To fetch work.
3/09/2014 3:44:30 AM | Milkyway@Home | Requesting new tasks for ATI
[Sep 2, 2014 5:47:03 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

Ah, so what you are essentially saying is that I cannot limit boinc CPU usage by project. I would really like WCG to use only 2 cores and allow the other 2 cores to run the 4 GPU tasks.

Yes you can by setting up an app_config.xml, with the newest 7.4 agent now offering additionally to specify how many tasks total for wcg are allowed to run at the same time.

David Anderson [Fri, 25 Jul 2014 22:49:12 +0000]
client: add <project_max_concurrent> option for app_config.xml

Lets you limit the number of running jobs over the whole project.
Note: this is not taken into account in work fetch.

[Sep 2, 2014 5:55:39 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

I have investigated the app_config.xml option before and found it to be quite confusing. Would you be able to show me how to implement this file?
[Sep 2, 2014 6:01:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

You simply place the app_config.xml file in: Boinc Data > projects > www.worldcommunitygrid.org. To activate it, you go into Boinc Manager > Advanced en click Read config files.
[Sep 2, 2014 6:14:10 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: WCG ignoring device manager.

Got it working :D
Cheers


Anyone got any idea on my additional question?
The Intel GPU underclocks itself when CPU tasks are running.
[Sep 2, 2014 6:24:16 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 15   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread