Posts by user666

1) Message boards : GPUs : limit / control gpu usage via boinc config files / non_gpu coprocessor (Message 61718)
Posted 19 Apr 2015 by user666
Post:
thanks so far. i believe its very bad one is unable to control / limit gpu usage via the boinc client. it should be implemented asap. a lot of people really want and need this option. i see no reason this is not realized by the devs.
2) Message boards : GPUs : limit / control gpu usage via boinc config files / non_gpu coprocessor (Message 61554)
Posted 12 Apr 2015 by user666
Post:
its strange that supposedly one is unable to limit or control gpu usage by opencl for example.

i had an idea and tried to play around with the coproc_info.xml where i halved the gpu specifications hoping it would define a limit for boinc but strangely i had not impact.

my basic idea was telling boinc false ideas about the gfxs specification so it would not torture it so much and thereby effectively reducing gpu load.

i cant imagine there is no way you cant control / limit gpu usage. im sure there is a way with the config files or something!

would be nice if we could figure it out, because id really love to have it run on 50% of my gpu, otherwise i have to disable gpu computing and i find that very sad due to that lack of control.

is it possible to run the gpu as non_gpu co-processor?

if so, it should adjust with cpu settings.

<coproc>
specify a coprocessor. Used in combination with the Anonymous platform mechanism. The element has the form
<coproc>
<type>some_name</type>
<count>1</count>
<device_nums>0 2</device_nums>
[ <peak_flops>1e10</peak_flops> ]
[ <non_gpu/> ]
</coproc>

The name given in <type> must match that in the <coproc> element in app_info.xml. <count> in the number of GPU instances, and <device_nums> is their device numbers. <peak_flops> is the GPU peak FLOPS; it can be omitted if your app_info.xml specifies estimated application FLOPS. If <non_gpu/> is specified, the coprocessor is not treated as a GPU; i.e. "Suspend GPU" does not affect it. This mechanism has two purposes: to provide fine-grained control of the coprocessors recognized by BOINC (NVIDIA, AMD, and Intel GPUs), and to let you use coprocessors not recognized by BOINC.

i tried to get it to work with a cc_config.xml file looking like this:

<cc_config>
<options>
<coproc>
<type>ATI</type>
<count>1</count>
<device_nums>0</device_nums>
<non_gpu/>
</coproc>
</options>
</cc_config>

im not sure if this is correct and working since my gpu load is still 0%. but also i did not use an app_info.xml. can someone clarify? im trying to use gpu as non_gpu co-processor.
3) Message boards : GPUs : GPU Throttle? (Message 61399)
Posted 4 Apr 2015 by user666
Post:
is it possible to run the gpu as non_gpu co-processor?

if so, it should adjust with cpu settings.

<coproc>
specify a coprocessor. Used in combination with the Anonymous platform mechanism. The element has the form
<coproc>
<type>some_name</type>
<count>1</count>
<device_nums>0 2</device_nums>
[ <peak_flops>1e10</peak_flops> ]
[ <non_gpu/> ]
</coproc>

The name given in <type> must match that in the <coproc> element in app_info.xml. <count> in the number of GPU instances, and <device_nums> is their device numbers. <peak_flops> is the GPU peak FLOPS; it can be omitted if your app_info.xml specifies estimated application FLOPS. If <non_gpu/> is specified, the coprocessor is not treated as a GPU; i.e. "Suspend GPU" does not affect it. This mechanism has two purposes: to provide fine-grained control of the coprocessors recognized by BOINC (NVIDIA, AMD, and Intel GPUs), and to let you use coprocessors not recognized by BOINC.

i tried to get it to work with a cc_config.xml file looking like this:

<cc_config>
<options>
<coproc>
<type>ATI</type>
<count>1</count>
<device_nums>0</device_nums>
<non_gpu/>
</coproc>
</options>
</cc_config>

im not sure if this is correct and working since my gpu load is still 0%. but also i did not use an app_info.xml. can someone clarify? im trying to use gpu as non_gpu co-processor.
4) Message boards : GPUs : GPU Throttle? (Message 61394)
Posted 4 Apr 2015 by user666
Post:
its strange that supposedly one is unable to limit or control gpu usage by opencl for example.

i had an idea and tried to play around with the coproc_info.xml where i halved the gpu specifications hoping it would define a limit for boinc but strangely i had not impact.

my basic idea was telling boinc false ideas about the gfxs specification so it would not torture it so much and thereby effectively reducing gpu load.

i cant imagine there is no way you cant control / limit gpu usage. im sure there is a way with the config files or something!

would be nice if we could figure it out, because id really love to have it run on 50% of my gpu, otherwise i have to disable gpu computing and i find that very sad due to that lack of control.



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.