While watching Task Manager's Details tab, sorted by CPU descending, I see that the acemd process is never starved for CPU, even though other running CPU tasks are (at times) starved. It's the and settings that determine how many tasks run at the same time on a given GPU, and how much CPU each task takes.Ĭome to think of it, in case I add more GPUs in the future, I'll probably go ahead and set arbitrarily low, to 0.001, for each of the apps, that way even if I had 3+ GPUs, a CPU core would never be reserved. Though I'm told the line can be omitted, I'd prefer not to risk it, so I just set it arbitrarily high, to 50. I just put it to 50 to ensure it never limits me, and to satisfy the spec found at. Since I only have 2 GPUs, and I'm only running 1 task per GPU, I could theoretically set it as low as 2 and it wouldn't have any effect.
I believe means "run up to this many tasks at once, of this application, across your entire computer" and the result is always 100% CPU utilization. The GPUGrid projects still get all the CPU they'd need/want (because their base priority is special), and when I happen to get GPUGrid tasks that don't use much CPU, my CPU tasks pick up the slack (Since 0.499 + 0.499 < 1.000, meaning that a CPU core is NOT reserved for GPUGrid). Essentially, I've set it up with 0.499 for cpu_usage, so that even when both video cards are crunching GPUGrid tasks, my CPUs are still kept busy. With that in mind, since I have 2 video cards and care very much about my other CPU projects, I have decided to use the following app_config.xml. Also, the GPUGrid processes appear to have been tweaked such that the base priority is "Below Normal", which is above "Low" (which CPU tasks use). When I watch some of the GPUGrid tasks run, I notice that some of them use a CPU all of the time, some tasks only use a CPU part of the time, and some don't really use much CPU. I have 2 nVidia GPUs (GTX 660 Ti, and GTX 460). While it's been demonstrated that you can mix apps from different projects and achieve better overall Boinc credits, it's very high maintenance and not something for the novice (not saying you are).Īs the project is largely Beta testing, it's really a bad time to be testing app_* and or overclocking. Even then there's only a moderate increase unless utilization drops to around 60%.Ī subsequent concern is the number of different task types run at GPUGRID typically there are two or three, but sometimes more, so any gain would only apply when you get two similarly low GPU utilizing tasks. In the past, I've tested this to exhaustion and at GPUGRID there is little or no gain unless GPU utilization drops below 80%.
Custom boinc config file trial#
Thanks for reporting on your trial Carlesa25 it confirms the status quo.
0 kommentar(er)
