1) Message boards : BOINC client : Multi-GPU multi-project scheduling oddity (Message 93487) Posted 2 Nov 2019 by jjv1001 Post: Wrong turn of phrase. The request for work was of course initiated by my client. I think something is off with the amount of work received but that really is not the issue. I'm entirely okay with a project doing CPU only work for a while although in this case the amount of jobs in the queue will never finish before the deadline. Actually now that I look at it I have three pages worth of "not started by deadline" cancellations so the current situation will probably fix itself in short order. The actual problem is the weird logic in stuffing the secondary GPU full of work while leaving the primary entirely empty. I do believe that the problem is platform independent and have actually seen it occasionally appear over the years and versions. But the platform is Win x64 and the client is currently 7.16.3. Should it matter the actual projects in question are A - Einstein, B - Milkyway and C - SETI I'll keep monitoring the logs. JJ

2) Message boards : BOINC client : Multi-GPU multi-project scheduling oddity (Message 93484) Posted 2 Nov 2019 by jjv1001 Post: I seem to be hitting some sort of a corner case with the scheduler. A quickish explanation: 6 projects, 3 of them have both CPU and GPU jobs. In order to maintain a balance between projects a limitation on concurrent jobs is imposed. Also project A is limited to GPU1 while project B is limited to GPU2. Project C is allowed on both. All GPU jobs are done fractionally to allow multiple jobs on a single GPU. Now the situation is that project A decided to send me a ton of CPU jobs. This combined with the limit on concurrent jobs forces the project to compute CPU work only. Now project A is running on CPU only, project B is still using GPU2 happily but project C seems to insist on also using GPU2 leaving the entire GPU1 idle. JJ

3) Message boards : BOINC client : BOINC not respecting exclusive application lists (Message 86450) Posted 5 Jun 2018 by jjv1001 Post: They are. The configuration has been basically unchanged for ages with no problems. But I'm 99% certain the problem lies outside BOINC. I'll keep digging. JJ

4) Message boards : BOINC client : BOINC not respecting exclusive application lists (Message 86405) Posted 1 Jun 2018 by jjv1001 Post: At some point on my main computer BOINC either stopped respecting exclusive CPU/GPU applications or is unable to monitor running processes. Unfortunately I don't know when exactly this stopped working since this is a fairly beefy machine. It could correlate to 7.10.2 but I'm not certain. The machine is running Win7 so this is unrelated to Win10 shenanigans. I haven't noticed anyone having the same issue so I'm basically asking if I'm alone with this issue. JJ

5) Message boards : BOINC client : Boinc client startup on Windows 7 Pro 64-bit (Message 51910) Posted 5 Jan 2014 by jjv1001 Post: Don't know if there's an elegant method and this is assuming that you're not using a service installation, but BOINC launches itself via registry 'Run' key. By default the launch anchor is in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run. You could move it to the equivalent key at HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run to make it launch for the current user only. All the normal caveats of touching the registry (Be absolutely sure you know what you're doing etc.) apply and updating BOINC will probably mess this up. JJ

6) Message boards : BOINC client : Multicore project resource share (Message 41647) Posted 15 Dec 2011 by jjv1001 Post: The hypothetical is basically an extremely simplified version of my situation. There have been times when my machines have been totally saturated with Milkyway n-body WUs until the project has gone down, which it has a habit of doing. At the moment the situation seems to be more equal and the only change is that the project updated the n-body application. This however shouldn't affect the scheduling which is handled by the core client. I do admit that there might be observational bias, but was hoping that someone could give me a simple yes or no for specialized multicore scheduling in the BOINC client. My interest is mostly academical since my machines are happily crunching away, but having already delved rather deep into the configuration options I was wondering if there was some setting that could affect the situation. JJ

7) Message boards : BOINC client : Multicore project resource share (Message 41635) Posted 14 Dec 2011 by jjv1001 Post: So apparently this is a mystery no-one knows the answer to :-) Still, to clarify my question: Say I'm running two projects with equal resource shares whose WUs take the same amount of time, but project A's WUs are singlecore and project B's multicore. If the multicore uses all 8 cores and BOINC decides to download ten new WU's, in my opinion, the distribution should be around 8/2 while it seems to be an even 5/5 split. This becomes especially problematic with projects like T4T that don't allow WUs to be queued. Of course multicore WUs are rare. I personally don't know any other project than Milkyway that uses them. JJ

8) Message boards : BOINC client : Multicore project resource share (Message 41499) Posted 6 Dec 2011 by jjv1001 Post: Can someone explain how multicore workunits are scheduled to run? I'm currently running Milkyway@Home N-Body workunits on an 8-core machine where they peg all the cores and it seems they are treated the same as single core WUs. Most of the time the only other projects that get any work done are the GPU projects. I'm using the 7.0.2 version on one machine and the latest stable on another and there seems to be no difference between them. JJ

---

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.