Top program sorted by normalized score

The Prover-Account Top 20
Persons by: number score normalized score
Programs by: number score normalized score
Projects by: number score normalized score

At this site we keep several lists of primes, most notably the list of the 5,000 largest known primes. Who found the most of these record primes? We keep separate counts for persons, projects and programs. To see these lists click on 'number' to the right.

Clearly one 100,000,000 digit prime is much harder to discover than quite a few 100,000 digit primes. Based on the usual estimates we score the top persons, provers and projects by adding ‎(log n)3 log log n‎ for each of their primes n. Click on 'score' to see these lists.

Finally, to make sense of the score values, we normalize them by dividing by the current score of the 5000th prime. See these by clicking on 'normalized score' in the table on the right.

normalizedprogramprimesscore
104261 Mihai Preda's GpuOwl [prp, special] 1 58.0015
77237 George Woltman's Prime95 [special] 44 57.7015
37554 Jean Penné's LLR [special, plus, minus] 4708 56.9804
15540 Yves Gallot's GeneFer [prp, special] 2548 56.0980
15466 Anand Nair's GFNSvCUDA sieve [sieve] 2546 56.0933
15434 David Underbakke's AthGFNSieve [sieve] 2550 56.0911
15409 Geoffrey Reynolds' srsieve [sieve] 2057 56.0896
8541 Pavel Atnashev's PRST [] 332 55.4995
5728 LLR2 [other] 1225 55.1000
5664 EMsieve [sieve] 104 55.0888
5387 Anand Nair's CycloSvCUDA sieve [sieve] 27 55.0385
5173 Yves Gallot's Cyclo [special] 34 54.9980
3516 Reynolds and Brazier's PSieve [sieve] 1595 54.6120
2700 Geoffrey Reynolds' gcwsieve [sieve] 51 54.3480
1399 MultiSieve/mtsieve [sieve] 37 53.6904
1291 Mikael Klasson's Proth_sieve [sieve] 9 53.6098
1288 Phil Carmody's 'K' sieves [sieve] 7 53.6078
1288 Paul Jobling's SoBSieve [sieve] 7 53.6078
784 OpenPFGW (a.k.a. PrimeForm) [other, sieve, prp, special, plus, minus, classical] 560 53.1118
158 Paul Jobling's NewPGen [sieve] 416 51.5076
 
 

Notes:

The list above show the programs that are used the most (either by number or score). In some ways this is useless because we are often comparing apples and oranges, that is why the comments in brackets attempt to say what each program does. See the help page for some explanation of these vague categories
normalized score

Just how do you make sense out of something as vague as our 'score' for primes? One possibility is to compare the amount of effort involved in earning that score, with the effort required to find the 5000th prime on the list. The normalized score does this: it is the number of primes that are the size of the 5000th, required to earn the same score (rounded to the nearest integer).

Note that if a program stops finding primes, its normalized score will steadily drop as the size of the 5000th primes steadily increases. The non-normalized scores drop too, but not as quickly because they only drop when the program's primes are pushed off the list.

Printed from the PrimePages <t5k.org> © Reginald McLean.