BRP6 Beta
18 Jan 2016 19:23:47 UTC
Topic 198384
(moderation:
I have been running the Beta app for BRP6 on my GTX660 since it came out and have been very pleased with it.
Now due to work availability issues over at Seti my GT430 is now crunching a BRP6 Beta also. GPU-Z is showing very poor utilization. My guess is Fermi cards don't like CUDA 5.5. I'll let'r run till it completes and then try a stock BRP6 and see what happens. Does anybody have any insight?
BRP6 Beta
)
The CUDA55 update of BRP6 was greatly beneficial for Kepler and Maxwell generation cards, but not helpful for earlier ones. I think that is a fair summary, though you can find lots of more detailed discussion by looking around here a little.
Well it finished and
)
Well it finished and validated. The run time was almost 8 1/2 hrs. The stock BRP6 is showing much better GPU utilization.
RE: Well it finished and
)
You now have a non-beta result and it looks like that one ran 8% faster. Have you tried to run more than one GPU job in parallel via the "utilization factor" setting in E@H#s web preferences? Also freeing one CPU core can help to increase overall throughput , especially when running more than one GPU task in parallel. The increased productivity will, in many cases, more than compensate for the loss of a CPU task running in parallel. I'd say it's worth a try.
HB
Isn't it time to promote
)
Isn't it time to promote those CUDA 5.5 applications (BRP6-Beta, BRP4G-Beta) from Beta stage to standard apps ?
We're running them for several months and it looks well..
-----
RE: RE: Well it finished
)
This little machine always is run with a free core and back in the days of BRP4 it did run 2 tasks at a time with a small degree of greater thru put but the video driver crashed every couple of days thrashing a workunit about 1/2 the time.
RE: Isn't it time to
)
I have thought for months that BRP6 Beta was ready for prime time but this shows to me That Fermi and earlier cards should be allowed somehow to stay with CUDA 32. Possibly using an automated process such as Seti uses or selecting it in your preferences, which means most users probably be unaware of.