Before I even begin, is the Quadro K 4000/4200/4400 (I'm not sure, trying to remember the model... without success) supported by GPU Grid?

If no, ignore the rest of this post.

But if yes, should I focus on the short or long WUs?

Also, the age old dillema: install as a service and have BOINC run without the need to have a person logged in, or only run it when someone is logged, but making use of the GPU.

From my extensive google browsing, this has been a problem, and to date, with no solution; however, I've seen a user claim (somewhere...) that versions 7.3.XX and higher have some kind of support for the feature, but I haven't seen any documentation about it anywhere else. Is it true?

Question number 3, is it possible to make a dual install, or dual config, or really any kind of sorcery, so that you can have BOINC crunching on CPU only when nobody is logged, but have access to the GPU once someone logs in?

Last question: does anyone know if F@H has support for any of these features? I'm not very good with F@H, all I know about is BOINC.


I mean, don't get me wrong, if I'm forced to choose, I'm pretty sure that the 16 threads Xeons take priority over the occasional work on the "weak" quadro cards. But if I can use both, I'd love to blow up the fuses of the building.. er, help the science a bit further.

I can answer your 1st question - yes, Quadro K4xxx is supported. I have run long runs on K4000 and K4200. But these GPUs have a weak cooling and thus reach high temperatures, so if you want to run GPUGrid there, make sure you have additional cooling.

Also, the age old dillema: install as a service and have BOINC run without the need to have a person logged in, or only run it when someone is logged, but making use of the GPU.

From my extensive google browsing, this has been a problem, and to date, with no solution; however, I've seen a user claim (somewhere...) that versions 7.3.XX and higher have some kind of support for the feature, but I haven't seen any documentation about it anywhere else. Is it true?

You can't install Boinc 'as a service' AND use the gpu for crunching

Question number 3, is it possible to make a dual install, or dual config, or really any kind of sorcery, so that you can have BOINC crunching on CPU only when nobody is logged, but have access to the GPU once someone logs in?

The newer Boinc versions, I think 7.3+, keep the gpu crunching even if you switch users, I'm not sure this answers your question but it does mean you can keep on 'blowing the switches' even when no one is logged in.

If it's a system that only you use then do a standard (non-service) installation, log on and just leave it logged on. You can lock Windows systems by pressing the Start key + L.
If other people use the system then you could configure Boinc to run only when they are not actively using the system (say after 3min of non use), but you can't allow the GPU to always run and the CPU to only run when the system is no in use.
If you can run 24/7 then go with the long tasks, otherwise stick to short tasks.
The Quadro K 4200 is ~75% faster than the 4000; 1344 vs 768 cuda cores. Both are Keplers and Power consumption is fairly low (122W & 108W).

Using remote desktop stops GPU tasks.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

If it's a system that only you use then do a standard (non-service) installation, log on and just leave it logged on. You can lock Windows systems by pressing the Start key + L.
If other people use the system then you could configure Boinc to run only when they are not actively using the system (say after 3min of non use), but you can't allow the GPU to always run and the CPU to only run when the system is no in use.
If you can run 24/7 then go with the long tasks, otherwise stick to short tasks.
The Quadro K 4200 is ~75% faster than the 4000; 1344 vs 768 cuda cores. Both are Keplers and Power consumption is fairly low (122W & 108W).

Using remote desktop stops GPU tasks.

Using VNC though does NOT stop gpu tasks, I use it all the time on my home network to log into all my others from my main one.

If the pc is in an area where it doesn't matter if it's logged in all the time you can turn the logging off thru Windows settings, I do that at my home but would NOT do that in a business. I even have mine setup to auto log me on when they restart. Most of my pc's are Boinc only machines with no mouse, keyboard or monitor hooked up to them, so auto logging on means they can just crunch 24/7.

A remote session through VNC or Team Viewer, will not make GPU tasks stop.
A remote session through Remote Desktop, as skgiven said, will make GPU tasks stop.

Chrome Remote Desktop works also. There are others that will work too. Just not Windows Remote Desktop.