So ... what am I not doing correctly? (Yes, I stopped BOINC Manager before executing the performance utility).

I`m using MSI Afterburner.
Works on nvidia also.

Thanks, Mike. Downloading...
EDIT: looks like this utility is successor of RivaTuner too.

MSI Afterburner works as a service? With out need to log on any user?

You need to log in.
GPU access is only allowed for a logged in user. So no service.

Windows Server 2003 (see opening post) is comparable to Windows XP - and Windows XP allows services to access the GPU, even when the service logs on using a different account than the foreground user.

I`m using MSI Afterburner.
Works on nvidia also.

Thanks, Mike. Downloading...
EDIT: looks like this utility is successor of RivaTuner too.

MSI Afterburner works as a service? With out need to log on any user?

Is it possible to flash required fan settings directly in GPU own BIOS memory?

Maybe you can try this instead:
http://www.nvidia.com/object/nvidia_system_tools_6.02.html

It's got a fan speed setting and the tools are tied into the NVIDIA Control Panel and can be made to work at startup, but I'm not sure about your Windows version.

Thanks all a lot!
As I understood this problem worth some consideration indeed. Auto-logon would be not good cause it's not home PC indeed.
Is it possible to flash required fan settings directly in GPU own BIOS memory ?

I can't say I am happy with the current state of things here on my favorite project, but I do know that they shall get better. After all, with over 13 years under my belt here, I have seen a lot of ups and downs.

Hello,

I did an interesting finding on the calculation time reported by SETI. I have now in the same computer both GTX 580 and GTX680.

The finding is that for GTX 580 the reported calculation time for one WU is roughly 1100 seconds while for the GTX 680 the calulation time averages around 250 (4,2 minutes) seconds.

When checking the Boinc Manager Tasks tab on active work Units the average calculation time for a WU is roughly 20 minutes (=1200s) (3 WU concurrently per card). So the calculation time reported is more in line with the GTX 580.

Why is the reported calculation time for GTX 680 differing so much?
Is GTX 680 idling somewhere and this is not reported in correctly?


http://setiathome.berkeley.edu/results.php?hostid=3299266&offset=0&show_names=0&state=2&appid=

Hello Fred, thank you very much for the program i use it from the first version you release.
I want to ask you which driver you use to complete 130sec for WU for GTX 295 and which WU from the list because my top time with 3 drivers tested same clock everything the same the best time for Core755/Shaders1655/Mem1255 is 188-190 sec with x41g for wu.
and my max settings are 805/1733/1255 the time for PG0444_v7 unit need 179 sec.

Agree my situation is simple with one host and one gpu. The project preference "use NVIDIA (or ATIa) gpu" only tells BOINC to not ask for gpu work. Turning it off will cause BOINC to only ask for cpu work. Definately not an automated approach - hope you find a better way.

I've noticed that 7.0.28 will keep asking for GPU work until it gets to about 1.25 days more than my min + additional setting, and even at that level it will ask for a few thousand seconds of GPU work. I use local preferences of 6 and .01. I don't get much CPU work until it gets to 7.25 days of GPU work per BOINCTasks' sum of estimated times. You can intervene and temporarily turn off GPU fetch in the SETI@Home project preferences (website). I have do this about once a week to rebalance the cache. Of course, that would affect all of your hosts unless you are using venues (home, school, etc).

And set at least the <sched_op_debug> logging flag in cc_config.xml so that you can see exactly what's going on when work is requested/received.

And what do you see in message log? Does BOINC client asks for CPU work and doesn't get it or it doesn't ask for CPU work?