Forum > GPU crunching
Unified installer add flops
Claggy:
DA has added COPROCS to HOST_INFO Changeset 19797
Claggy
Edit: and after Changeset 19798 get_host_info() GUI RPC now contains GPU info
cristipurdel:
--- Quote from: Claggy on 06 Dec 2009, 08:27:42 pm ---DA has added COPROCS to HOST_INFO Changeset 19797
Claggy
--- End quote ---
In simple English, this would mean the projects which run on the GPU will improve in which way?
efmer (fred):
--- Quote from: Jason G on 06 Dec 2009, 04:25:51 pm ---
--- Quote from: Fred M on 06 Dec 2009, 04:13:43 pm ---...
It looks these values don't have much to do with the actual calculation speed. More like theoretical values out of the sales brochure.
...
--- End quote ---
Absolutely.
[rant]
I actually got a little agitated when I installed Boinc 6.10.18 on my system & noticed it was claiming ~.~317GFlops 'peak' ... ( the words 'when hell freezes over' came to mind ;) Then I had a good laugh about it and felt much better). Of course with memory bound algorithms like larger FFT sizes, on that hardware, real world performance is more like 18-20GFLops, around twice that of each of my CPU Cores with the same problem. I've little doubt that kernels that do multiple redundant operations on the same data repeatedly, sitting in registers, on register sized (very small, ~8k total IIRC) datasets could acheive that kind of throughput ... The dumb thing is that sounds like graphics frame by frame processing more that general purpose computation[/rant]
I'm fairly certain the syntheic estimates shoudl be good enough, provided we scale the number appropriately to a realistic range... but there is the alternative of benching with real code if we find better accuracy is needed (which I doubt, but the option is there).
Jason
--- End quote ---
We probably could get a good estimate on the performance by using the number of processor cores and clock speed. And maybe the type of cores used etc.
The best way would be to run a small WU and see how long it takes to process, nothing beats the real world.
But it is the question of need, the flops don't need to be 100% accurate. I don't think a 20% change will do much, the WU will vary in time anyway.
Using the CudaApi, get the cores, clock and make our own more realistic formula.
Jason G:
--- Quote from: Fred M on 07 Dec 2009, 03:26:38 am ---...
Using the CudaApi, get the cores, clock and make our own more realistic formula.
--- End quote ---
Agreed. Let's try the easy way, and try predict indicators that show whether it'll be good enough, or needs the extra effort. Hopefully I'll have my build environment back up and functioning soon ( In the middle of Win7 migration after HDD death ::) ) so will be able to start making some small test pieces (.exe) with flop estimate outputs to experiment with in the installer scripts.
Jason
Richard Haselgrove:
--- Quote from: Claggy on 06 Dec 2009, 08:27:42 pm ---DA has added COPROCS to HOST_INFO Changeset 19797
Claggy
Edit: and after Changeset 19798 get_host_info() GUI RPC now contains GPU info
--- End quote ---
No reply to my question on boinc_alpha, but it obviously had the desired effect!
I'll grab one as soon as there's a build available, and let you see it so you can decide if it's any use.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version