Top persons sorted by score
(Another of the Prime Pages' resources)
The Largest Known Primes Icon
  View this page in:   language help
 
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.

rankpersonprimesscore
663 Paul Rodriguez 2 43.7075
664 F. Javier Sánchez 2 43.7066
665 Michael Wild 1 43.7046
666 Andreas Heinz 1 43.6926
667 Koen van Gorp 1 43.6881
668 Andrey Dorovskikh 2 43.6863
669 Max Vassalli 2 43.6848
670 Seppo Parviainen 2 43.6827
671 Yoshinari Sumi 1 43.6827
672 Maarten de Jong 1 43.6736
673 Brandon Letzin 1 43.6656
674 John Chadwick 1 43.6656
675 Billy Cain 2 43.6578
676 Jorge M. G. Marafuga 1 43.6557
677 Michael Martinez 1 43.6531
678 Brendan Gallagher 1 43.6515
679 Mike Lehmann 1 43.6497
680 Peter Riesen 1 43.6491
681 Christophe Hippeau 1 43.6462
682 Daniel Skoog 1 43.6459

move up list ^
move down list v

Notes:


Score for Primes

To find the score for a person, program or project's primes, we give each prime n the score (log n)3 log log n; and then find the sum of the scores of their primes. For persons (and for projects), if three go together to find the prime, each gets one-third of the score. Finally we take the log of the resulting sum to narrow the range of the resulting scores. (Throughout this page log is the natural logarithm.)

How did we settle on (log n)3 log log n? For most of the primes on the list the primality testing algorithms take roughly O(log(n)) steps where the steps each take a set number of multiplications. FFT multiplications take about

O( log n . log log n . log log log n )
operations. However, for practical purposes the O(log log log n) is a constant for this range number (it is the precision of numbers used during the FFT, 64 bits suffices for numbers under about 2,000,000 digits).

Next, by the prime number theorem, the number of integers we must test before finding a prime the size of n is O(log n) (only the constant is effected by prescreening using trial division).  So to get a rough estimate of the amount of time to find a prime the size of n, we just multiply these together and we get

O( (log n)3 log log n ).
Finally, for convenience when we add these scores, we take the log of the result.  This is because log n is roughly 2.3 times the number of digits in the prime n, so (log n)3 is quite large for many of the primes on the list. (The number of decimal digits in n is floor((log n)/(log 10)+1)).