Posts by Flow

1) Message boards : BOINC client : Why Cuda doesn't work on vista when Boin run in "protected application execution"? (Message 28524)
Posted 6 Nov 2009 by Flow
Post:
One could separate the CPU WUs from the GPU WUs, so that the CPU tasks run under the boinc service with the boinc special account and the GPU WUs simply run under the boinc manager in the user context, as before.

This would increase the security, as only the GPU WUs have access to the user data. Also the CPU WUs would start even if there is no user session.

Of course, an implementation of the session 0 service should be the golden goal. ;)

2) Message boards : BOINC client : CUDA and noisy graphics cards (Message 23019)
Posted 10 Feb 2009 by Flow
Post:
2. An option which just stops crunching on the GPU would be nice

Already requested in ticket [trac]#842[/trac]

I was not aware of that ticket. But it goes into the right direction. BOINC needs separated settings for CPU and GPU crunching. And options to suspend working (on CPU and/or GPU) if some defined executables are running.

3. An integration with the BOINC account managers, so the user could setup some template configurations, share them among themselves, and activate them on their BOINC clients.

You should ask the Account Manager maintainers for that.

I think the BOINC dev´s first need to implement the basic options.

4. The "exclusive apps" should be categorized (eg. Games, Movie Players, CAD Applications)

Why? Now you just fill in what application should be exclusive. Isn't that easier? How many different exclusive_app flags do you want to choose from in the end? [...]

Well, my ideal conception would be a menu in BAM with predefined "exclusive app" templates, which could contain for exmaple, well-known game .exe files. So that lazy persons (like me), could just select the template in BAM, instead of searching and defining their game files. Which could be a lot, at least in my case. ;-)
The "exlusive_app" templates should also be separated between CPU and CoProcessor/GPU crunching.
IMHO the exclusive_app tag in cc_config isn´t really the right way to handle this situation.

Flow
3) Message boards : BOINC client : CUDA and noisy graphics cards (Message 23014)
Posted 10 Feb 2009 by Flow
Post:
After using GPUGrid for a while, i think this request could be "optimized".
I replaced my old 9800GTX+ with an Asus EN98000GTX+ Dark Knight, which has a silent FAN on it. So i could run BOINC allways, but there is one situation where i dont want to have any crunching application in my GPU Memory: When I am gaming.
I found out, that with <exclusive_app> in cc_config.xml (http://boinc.berkeley.edu/wiki/Client_configuration) there is a option to stop BOINC from crunching, if there is a game executable running. This is definitely a good start.
But i have some suggestions:
1. It should be configurable with the BOINC Manager
2. An option which just stops crunching on the GPU would be nice
3. An integration with the BOINC account managers, so the user could setup some template configurations, share them among themselves, and activate them on their BOINC clients.
4. The "exclusive apps" should be categorized (eg. Games, Movie Players, CAD Applications)


What do you think?

Flow
4) Message boards : BOINC client : BOINC as Service with Vista and CUDA (Message 22777)
Posted 30 Jan 2009 by Flow
Post:
I wonder when we will be able to install BOINC as Service in a Vista/CUDA environment. Is this even possible (in the near future)?

Flow
5) Message boards : BOINC client : CUDA and noisy graphics cards (Message 21898)
Posted 17 Dec 2008 by Flow
Post:
Just bought a new PC (Q6600, 9800GTX+). I usually let BIONC run all the time, but with CUDA Apps and the noisy fan of the 9800GTX+ Graphics Card the PC becomes very loud. The CPU Fan is really quiet, it is just the GPU Fan. If i turn of BOINC, the GPU Temp drops and the GPU Fan falls silent.
So I wonder, if it is possible to run CUDA apps only after a specified time (away time), while the CPU Apps stay active all the time?




Copyright © 2023 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.