Expected GPU Magnitude Update (17-2-2018)

Over the last week I have been working on improving the estimates for expected magnitude generated by my scripts by incorporating task data downloaded from the project websites. This has been proving more difficult than anticipated, due to inconsistent reporting of CPU time between projects and contradictions in which CPUs get assigned multi-threaded tasks (i.e. YAFU assigning a quad core CPU 16 thread work units).

After a week filled with frustration I decided to give up on adding task data to the CPU tables for now and move on to the GPU tables. Luckily this went much smoother. Top hosts where determined using the method from my previous script. The task data for these hosts where downloaded. The task data was used to calculate credit/second by dividing the credits for each task by the wall time. This was then used to calculate an estimate of the magnitude.

Today we also have a special table that is just for fun… server and prosumer GPUs

Results: Nvidia

The usual project advice applies here.

  • Run the PPS-sieve subproject on PrimeGrid .
  • Running CUDA tasks on Enigma requires Windows

nvidia.png

Results: AMD

And the standard AMD advice:

  • Run Milkyway if you have a GPU using the Tahiti architecture (including the R9 280/280x)
  • GPU Grid requires CUDA (Nvidia)
    amd.png

Results: Server/Prosumer

This section is just for fun. There isn't nearly enough data to say whether or not these number are accurate. Just knowing that someone is using them for BOINC projects is ridiculously awesome.

otherGPU.png

H2
H3
H4
Upload from PC
Video gallery
3 columns
2 columns
1 column
18 Comments