Chrome vs Desktop

[FrankV]

I've dabbled in Folding@Home and BOINC for many years now. I start and stop for a lot of reasons. I just built a new, much more capable desktop and want to do folding@home -- at least some of the time my computer is on (it's mainly for gaming). 

 

Listed on this forum, I found that there is a Chrome plugin that basically runs the program in my browser. This has advantages for my use case but what is the disadvantage? So far, the principle one I see is it doesn't seem to use my GPU... 

 

Any advantages of the desktop app you'd point out (over the Chrome plugin version)? 

[blackmage1134]

yes the Chrome plugin just does CPU and smaller work units far as i know. 
the full install does CPU and GPU. with larger WU sometimes. 
if you want to get more points you will need to use the GPU. 

[FrankV]

19 hours ago, blackmage1134 said:

yes the Chrome plugin just does CPU and smaller work units far as i know. 
the full install does CPU and GPU. with larger WU sometimes. 
if you want to get more points you will need to use the GPU. 

Ok, thanks. Since posting this, I've settled on running the full Folding@home on my gaming computer (which obviously has an actual GPU) and I use the browser version for my work laptop set at Light folding power while I'm working. 

 

I tried the full version on my laptop but it's too aggressive even on light; too much throttling and I get graphical latency (it has a NVidea NVS GPU). 

 

So, for others visiting, it's notable that the windows client is a bit more resource intensive across all folding settings than the chrome plug in version. 

[blackmage1134]

sounds like a good plan. and always good to see active people on the f@h team.