|
1)
Message boards :
BOINC client :
GPU work fetch bug in 7.0.25
(Message 43380)
Posted 10 Apr 2012 by ReverseInternet.com Post: Nope - doesn't help. It seems that in 7.0.25 <ignore_ati_dev>0</ignore_ati_dev> on Crossfire system is treated the same way as no GPUs |
|
2)
Message boards :
BOINC client :
GPU work fetch bug in 7.0.25
(Message 43377)
Posted 10 Apr 2012 by ReverseInternet.com Post: Sent logs to David. Meanwhile is there any way to absolutely force BOINC to get new GPU WUs regardless of anything in the config, scheduler, etc? |
|
3)
Message boards :
BOINC client :
Intelligent GPU computing control (crossfire/sli)
(Message 43375)
Posted 10 Apr 2012 by ReverseInternet.com Post: Yes, I know about this feature. I appreciate all the hard work that developers have put into developing BOINC. But still, you need to add things to this list. On the other hand I've set up the system only once and it works. Are there any plans to implement the logic of switching between one and two GPUs based on user activity? |
|
4)
Message boards :
BOINC client :
Intelligent GPU computing control (crossfire/sli)
(Message 43368)
Posted 10 Apr 2012 by ReverseInternet.com Post: I'm running a Crossfire ATI setup and noticed that I can crunch numbers on the second GPU pretty much anytime except when I'm playing some 3D game. Not wanting to maintain an up-to-date list of all my games in bonic cc_config file, I've created a small app that suspends BOINC any time when full screen app is started - http://www.everydayinternetstuff.com/2012/04/suspend-boinc-when-full-screen-game-is-running-better-than-exclusive_app/ I'm currently testing the next version of this app that swaps cc_config file whenever user becomes idle/active and gracefully restarts BOINC so that both crossfire GPUs could be used when the user is idle but only the secondary one when user is active. If anyone is interesting in this I can share the updated program. I would like to have it privately tested a bit before making it generally available. Ping me if you are intersted. Since the app works by swapping out config files, you can customize BOINC behavior in any way based on idle/active |
|
5)
Message boards :
BOINC client :
GPU work fetch bug in 7.0.25
(Message 43367)
Posted 10 Apr 2012 by ReverseInternet.com Post: I'm running a system with crossfire ATI GPUs. When I use the computer I have the main GPU disabled for BOINC by adding <ignore_ati_dev>0</ignore_ati_dev> to cc_config.xml. In 6.12 that seemed to work fine. In 7.0.25 it still does except for the fact that BOINC refuses to download new GPU work because: 4/9/2012 10:03:48 PM | Milkyway@Home | [work_fetch] ATI: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by configuration file) Fixing this bug would be nice, since it would allow me to crunch on the secondary GPU all the time except when I'm gaming (which is not that often). Let me know if you need more data from logs. |
|
6)
Message boards :
Questions and problems :
Use only one GPU when user is active
(Message 37185)
Posted 15 Mar 2011 by ReverseInternet.com Post: Is it possible to tweak BOINC so that it would use only one of two crossfired ATI GPUs (that BOINC detects as two separate cards) when the user is active and use both when computer is idle? |
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.