GPU utilization factor settings - lowest working value
11 Jan 2025 10:47:29 UTC
Topic 231956
(moderation:
What is the lowest working value for the 3 GPU utilization factor settings?
Cause I have set them all to 0.1, from the default 1.0, which should give me 10 GPU tasks running at the same time, but I still only have 2 tasks.
And if I set the values to 0,33, I got 3, 0.25, I got 4, but then 0.20, I still only got 4.
Hope somebody can answer this question :)
Ncard00 wrote: What is the
)
If you are changing it on the website, then it will take some time to see the impact. If you use an app_config file, it will be immediate. I am not sure what the lowest can actually be but I do know that running any of the current tasks at 10x will not be efficient. I am not sure that was your goal or just something you tried to see if changing the setting would work.
I am just curious. And also,
)
I am just curious. And also, I've now also tested this on my RTX 3060, and setting the value to 0.1, it's now running 10 tasks at the same time, but on my M4 Mac Mini, I am still only getting 2 tasks at once on this value.
And also, the warning about only changing these settings is you know what you're doing, doesn't make sense to me. If you have enough cooling, the fan will just spin faster, and if you don't, it will just thermal throttle, how they're designed. And for every additional task, the utilization is split accordingly, so 10 tasks means only 10% per task, so please also, if possible, explain the necessity of this warning, as well as helping me out with my Nvidia GPU vs Apple SIlicon GPU core utilization issue :)
Ncard00 wrote: I am just
)
I think 2 is all you are going to get on your M4 Mac Mini. It uses Unified Memory. I too have an M4 and that's all I can get out of it. Most times your most efficient setting will be .5 for most GPU tasks. Sometimes .3.
The warnings come from the "old" days when cards did not self throttle. Not so many years ago you could melt down a card by pushing it too hard as it had no "self-preservation". They have probably left the warning in there for those with older systems.
Phil
I thought I was wrong once, but I was mistaken.
Thanks for the reply.
)
Thanks for the reply.
Ncard00 wrote:What is the
)
Just so you know, you should be using an app_config.xml file.
Also, using a 0.1 setting to get 10 tasks MAY get get you 10 tasks, and then again it may not. When setting the 0.1 in your app_config.xml file, your are requesting BOINC to honor your your request, but BOINC may not actually do so.
When choosing how many tasks to run, monitor the times closely. A "1.0" task should be your baseline. A "0.5" will be for two tasks, and the time will be two times the value of "1.0" - OR LESS! When running tasks in multiples, you should always divide the time by the appropriate number (i.e. 0.5 = 2 tasks, 0.33 = 3 tasks, and so on). The product received by doing this should always be less than your baseline of "1.0", meaning that you are increasing efficiency by doing so. When it becomes equal to or more than your baseline, you have reached the point of reducing your efficiency - even though you may be running more tasks.
HTH
Proud member of the Old Farts Association