Primegrid PPSE Benchmarks

[Skillz]

This sub project is normally best to run single threaded. Current FFT length is around 1.5MB in size so it easily fits in the L3 cache domain with as many physical cores as a CPU has, in most cases.

Their is an up-coming Primegrid challenge series challenge in 4 days running this project so I am benchmarking a few of my hosts to get an idea of what I'll be able to bring to the table.

The current number I am using is a number I pulled off Primegrid's site. This number was completed on July 21st, 20206

Date Completed	Number	Points per task
July 21, 2026	5235*2^2378137+1	144.87

Will update the number for future challenges/benchmarks since this particular subproject's candidates progress very quickly.


Preferences notes about this sub project pulled from Primegrid.com

Proth Prime Search Extended LLR (PPSE)
k·2n+1 for 1200<k<10000
NOTE: PPSE tasks have smaller 'n' values and therefore are shorter than PPS tasks.

Supported platforms:

• Windows: 32 bit, 64 bit
• Linux: 32 bit, 64 bit
• Mac: 64 bit
• Multi-threading is supported but is NOT recommended. Click here to set the maximum number of threads.
• Uses fast proof tasks so no double check tasks are needed. Everyone is "first"!

Deadline: 4 days (up to 30 days)
Recent average CPU time: 0:38:53
FFT sizes: 160K to 192K (uses up to 1536K cache per task)

 

[Skillz]

This is a Minisforum BD795i SE, I only ran these tests once. This is not an average of multiple tests.


This is a 16 core, 32 thread processor. I ran 16 tasks simultaneously on physical cores only and 32 tasks on all threads simultaneously.

Physical cores only is a bit faster on this host.

──────────────────────────────────────────────────────────────────────────────────────
                                   BENCHMARK SUMMARY
                                    Ryzen 9 7945HX
 Work Unit:                                               Proth Prime Search Extended
 Number Tested:                                                      5235*2^2378137+1
 Points per Task:                                                              144.87
 Benchmark Duration:                                                          10m 39s
 L3 Cache:                                                                    1.50 MB
 Affinity:                                                                  ascending
──────────────────────────────────────────────────────────────────────────────────────
       CPU Config         │    Task Duration    │   Tasks per Day  │    Estimated PPD
──────────────────────────────────────────────────────────────────────────────────────
  16 Tasks x  1 Threads   │       0:15:54       │     1447.736     │          209,733★
  32 Tasks x  1 Threads   │       0:34:07       │     1350.520     │          195,649
──────────────────────────────────────────────────────────────────────────────────────

 

[Skillz]

This is a Epyc 9654 CPU. Only one test, not an average.

This is a 96 core, 192 thread CPU. Running 96 tasks on all physical cores and then 192 tasks on 192 threads.

Again physical cores are faster, but a lot faster in this case. A whole lot faster. Kind of weird that the 7945HX was so much closer.

──────────────────────────────────────────────────────────────────────────────────────
                                   BENCHMARK SUMMARY
                                     EPYC 9654 96
 Work Unit:                                               Proth Prime Search Extended
 Number Tested:                                                      5235*2^2378137+1
 Points per Task:                                                              144.87
 Benchmark Duration:                                                          12m 24s
 L3 Cache:                                                                    1.50 MB
 Affinity:                                                                  ascending
──────────────────────────────────────────────────────────────────────────────────────
       CPU Config         │    Task Duration    │   Tasks per Day  │    Estimated PPD
──────────────────────────────────────────────────────────────────────────────────────
  96 Tasks x  1 Threads   │       0:26:27       │     5225.872     │          757,072★
 192 Tasks x  1 Threads   │       3:19:27       │     1386.128     │          200,808
──────────────────────────────────────────────────────────────────────────────────────

 

[Skillz]

This is a dual EPYC 9B14 host. Again I only ran the test once so no averages.

Same as above, but its two 96-core CPUs with a combined 384 threads. I again ran tasks on all physical cores, 192 of them, then again on all the threads of which their are 384 of them.

──────────────────────────────────────────────────────────────────────────────────────
                                   BENCHMARK SUMMARY
                             AMD EPYC 9B14 96-Core Pro...
 Work Unit:                                               Proth Prime Search Extended
 Number Tested:                                                      5235*2^2378137+1
 Points per Task:                                                              144.87
 Benchmark Duration:                                                          12m 27s
 L3 Cache:                                                                    1.50 MB
 Affinity:                                                                  ascending
──────────────────────────────────────────────────────────────────────────────────────
       CPU Config         │    Task Duration    │   Tasks per Day  │    Estimated PPD
──────────────────────────────────────────────────────────────────────────────────────
 192 Tasks x  1 Threads   │       0:21:48       │    12682.180     │        1,837,267★
 384 Tasks x  1 Threads   │       1:09:46       │     7925.336     │        1,148,143
──────────────────────────────────────────────────────────────────────────────────────

Here the 384 tasks run is much closer to the physical cores only run. While also being over 5x more than the single socket setup despite only having twice as many CPUs running. Something is a bit off here. I am going to rerun the single socket system. Maybe something was running while the threaded test run was going that skewed the results.