Edit: you can install w/o completing WUs. Just quit the client (not the x), run installer (it will ask you to uninstall old version, make sure not to check the "data" box, then run installer again), resume folding.
Release notes
v7.1.22:
Added proxy support with authentication types: none, basic & digest.
Added proxy configuration tab to FAHControl.
v7.1.23:
Fixed bug caused by ignoring WU return code after a quick pause/unpause.
Set default verbosity to 3.
Explictly white-list Fermi GPUs & downgrade if CUDA driver is insufficient.
Added new GTX 470, 485 and 590 to GPU white-list.
Moved FAHControl single app port within 0-65535 range. #604.
Filtered out 'Theater' from GPU list.
White-listed Nvidia Quadro G8x cards.
Move all ATI R700s GPUs to species 3 and R800s to species 4.
Don't allow passwordless access even if password is not set.
Don't automatically allow IPs in command-allow-no-pass.
Don't call battery status code if not necessary.
Release resources related to battery query in OSX. #593
Allow changing the number of CPU threads mid run but warn. #292
Fixed client new and client connection options saving. #617
Lock database on startup to stop multiple runs of FAHClient in same dir.
Pass '-service' option to core when running as a Win32 service. #592
Fix permissions for All Users Windows install. #595.
v7.1.24:
Don't download a new WU if max-units is reached. #607
Added GeForce GTX 460 SE to the white-list.
Fixed 'core-priority' in FAHControl.
Fixed options save.
Don't allow changing 'local' client name or IP.
Don't try to autostart the local client once online.
Fix permissions problem in RPM. #627
Hide 'Status' tab in novice mode.
Added project info. In novice mode only by default
What kind of points are you guys getting with the beta? I'm getting around 700 points for an SMP WU and about 1800 for a GPU WU. Don't know about the GPU side of things, but the SMP side seems really low to me.
Use this website to see what PPD you are getting, because the points you see displayed in the FAHControl are not accurate as far as I can tell. Probably due to the way they calculate over whole time instead of last three frames etc. GPU isn't nearly as bad because the WUs go so quickly.
Yeah, I stopped the GPU client and now my SMP client shot back up to 5k ppd. Seems the GPU leak is still pretty bad. I guess I'll wait til the 11.4 drivers are released so I can follow that other optimization guide. Not wanting to run beta drivers on my desktop.
So, I got a 6970 yesterday and installed drivers etc. Definitely a lot of processor leak to work on and the a16 core is NOT designed to use environment variables to improve performance (my computer froze up after I tried to put some in). In theory, the a16 core would not have noticed them (as the a11 core is all that should be affected), but that was not my result. Sometime next week I'm going to have to rebuild my server box and put by Nvidia cards back in action.
They definitely have a lot of stuff to work out for Radeon GPUs still. Not being able to play some games or watch a video while folding is very discouraging, in addition to the still-extant large processor leak. Occupying an entire core compared to <1% utilization for Nvidia is sad.
Beta 5 dropped on the 10th for those who are using it or want to see what the next interface will look like
"Some of the highlights of this beta are log filtering, significant Linux and OSX package improvements and improved networking. This release brings us very close to the next phase where we will start to recommend the v7 client on the http://folding.stanford.edu/ front page. Only a few issues remain before we commit to this next step. The most important of which is improved ETA/PPD calculation, which I am working on right now."
Source and download (remember, this is available for Windows, OSX, Mint/Debian/Ubuntu, and Red Hat/Fedora/CentOS)
If your current setup is working without issues, there is no advantage points wise. The advantage for new users will be a highly automated setup process (i.e. none of the command line stuff I asked you to do), with automatic detection of GFX cards and settings. There is a segmentation of what is available to change depending on the "expertise" level you set, making it harder to mess up settings via obscurity.
In theory, monitoring can be done within the FAHControl GUI of remote clients, but I still vastly prefer the HFM.NET interface at this time for that functionality (no PPD total for all monitored machines is one example, better PPD calculation on HFM is another). HFM will be updated to work with v7 clients, but I have not seen any beta version of this thus far (I just checked their website and it indicated that they are working on it, with active changes in the last 48 hours towards this goal, but have not released anything publicly)
just installed v7 beta on the i7 machine for shits and giggles and I can now run SMP on that machine because it makes it easy to limit the number of cores being used therefore bringing my temps into reasonable range until I can get a new HSF
just installed v7 beta on the i7 machine for shits and giggles and I can now run SMP on that machine because it makes it easy to limit the number of cores being used therefore bringing my temps into reasonable range until I can get a new HSF
For future reference, the cmd line way of limiting cores is to change the "advanced options" line from "-smp -verbosity 9" to "-smp # -verbosity 9" (which I believe works with odd numbers, but I have never set that up personally)
This i7 950 is blowing through the first unit in the queue with only 3 cores set to fold, can't wait to see what is will be once I can run full bore and not be in the mid 80s C or higher range. Dumb stock cooler.
I get a corrupted client box when I fold w/ V7 on my GPU. If I just fold with the SMP alone on the CPU everything is fine. If I fold with both it will run fine all night but sometime during the day the F@h display box with get corrupt with little boxes in place of the text. Both clients at that point will start turning EUE.
Anyone else have this issue ...should I try the V6 client?
Comments
https://fah-web.stanford.edu/projects/FAHClient/wiki/BetaRelease
Edit: you can install w/o completing WUs. Just quit the client (not the x), run installer (it will ask you to uninstall old version, make sure not to check the "data" box, then run installer again), resume folding.
Release notes
v7.1.22:
- Added proxy support with authentication types: none, basic & digest.
- Added proxy configuration tab to FAHControl.
v7.1.23:- Fixed bug caused by ignoring WU return code after a quick pause/unpause.
- Set default verbosity to 3.
- Explictly white-list Fermi GPUs & downgrade if CUDA driver is insufficient.
- Added new GTX 470, 485 and 590 to GPU white-list.
- Moved FAHControl single app port within 0-65535 range. #604.
- Filtered out 'Theater' from GPU list.
- White-listed Nvidia Quadro G8x cards.
- Move all ATI R700s GPUs to species 3 and R800s to species 4.
- Don't allow passwordless access even if password is not set.
- Don't automatically allow IPs in command-allow-no-pass.
- Don't call battery status code if not necessary.
- Release resources related to battery query in OSX. #593
- Allow changing the number of CPU threads mid run but warn. #292
- Fixed client new and client connection options saving. #617
- Lock database on startup to stop multiple runs of FAHClient in same dir.
- Pass '-service' option to core when running as a Win32 service. #592
- Fix permissions for All Users Windows install. #595.
v7.1.24:Use this website to see what PPD you are getting, because the points you see displayed in the FAHControl are not accurate as far as I can tell. Probably due to the way they calculate over whole time instead of last three frames etc. GPU isn't nearly as bad because the WUs go so quickly.
"Some of the highlights of this beta are log filtering, significant Linux and OSX package improvements and improved networking. This release brings us very close to the next phase where we will start to recommend the v7 client on the http://folding.stanford.edu/ front page. Only a few issues remain before we commit to this next step. The most important of which is improved ETA/PPD calculation, which I am working on right now."
Source and download (remember, this is available for Windows, OSX, Mint/Debian/Ubuntu, and Red Hat/Fedora/CentOS)
In theory, monitoring can be done within the FAHControl GUI of remote clients, but I still vastly prefer the HFM.NET interface at this time for that functionality (no PPD total for all monitored machines is one example, better PPD calculation on HFM is another). HFM will be updated to work with v7 clients, but I have not seen any beta version of this thus far (I just checked their website and it indicated that they are working on it, with active changes in the last 48 hours towards this goal, but have not released anything publicly)
Anyone else have this issue ...should I try the V6 client?