Team drive #13: k=400-600 n=1M-2M
 

This is team drive #13 for No Prime Left Behind. We will be searching all k=400-600 for n=1M-2M.

A PRPnet server will be processing a large part of the range. See [URL="http://www.mersenneforum.org/showthread.php?t=12224"]this thread[/URL] for information on our currently operating PRPnet servers. The info specific to this server that needs to be entered into your prpclient.ini file is:

server=G9000:100:1:noprimeleftbehind.net:9000

[B]For manual reservations, please request a file from the admins and we will send it to you. It is requested that manual reservations take no longer than ~3 weeks and that they be [/B][B]in multiples of no less than n=100.[/B]

Please report all primes found in [URL="http://www.mersenneforum.org/showthread.php?t=9891"]Report all k<=1001 primes here[/URL] thread. For manual ranges, please report all reservations/statuses/completions for this drive in this thread, and post all results files in this thread or send them to Gary at: gbarnes017 at gmail dot com.

Please report all top-5000 primes with a project ID of 'NPLB'.

New primes found from drive #13:
[code]
Prime found by
591*2^1611590-1 odicin
425*2^1609200-1 odicin
411*2^1607574-1 odicin
471*2^1604233-1 Trilo
595*2^1594415-1 unconnected
427*2^1593361-1 MyDogBuster
555*2^1591677-1 MiHost
427*2^1590349-1 MiHost
551*2^1583718-1 unconnected
433*2^1583059-1 unconnected
471*2^1582593-1 unconnected
449*2^1579160-1 unconnected
427*2^1577169-1 unconnected
557*2^1575504-1 unconnected
557*2^1571700-1 unconnected
597*2^1563213-1 odicin
541*2^1519465-1 Mini-Geek
449*2^1516108-1 Mini-Geek
465*2^1504138-1 Mini-Geek
551*2^1501694-1 Mini-Geek
595*2^1494593-1 mdettweiler
477*2^1489922-1 gamer007
527*2^1489120-1 mdettweiler
567*2^1484069-1 gamer007
559*2^1478821-1 mdettweiler
545*2^1478786-1 mdettweiler
527*2^1468300-1 Mini-Geek
475*2^1464057-1 juhehe
591*2^1458622-1 Mini-Geek
489*2^1456683-1 juhehe
413*2^1456498-1 Mini-Geek
513*2^1452354-1 Mini-Geek
459*2^1448999-1 Mini-Geek
499*2^1434643-1 Mini-Geek
429*2^1428961-1 Mini-Geek
501*2^1428194-1 unconnected
441*2^1422099-1 Mini-Geek
529*2^1421561-1 gd_barnes
473*2^1418790-1 gd_barnes
555*2^1414837-1 Mini-Geek
457*2^1413589-1 gd_barnes
543*2^1406895-1 Mini-Geek
549*2^1406577-1 Mini-Geek
515*2^1398708-1 Mini-Geek
573*2^1397559-1 unconnected
555*2^1395429-1 Mini-Geek
459*2^1387776-1 unconnected
593*2^1386914-1 gamer007
413*2^1381686-1 gamer007
481*2^1374765-1 gamer007
585*2^1366140-1 vaughan
411*2^1363094-1 vaughan
441*2^1350261-1 gamer007
587*2^1333710-1 gamer007
411*2^1318421-1 Mini-Geek
513*2^1318074-1 Mini-Geek
567*2^1298854-1 gd_barnes
507*2^1295094-1 gd_barnes
563*2^1293468-1 gd_barnes
475*2^1291353-1 gd_barnes
475*2^1290255-1 gd_barnes
527*2^1287756-1 gd_barnes
453*2^1283560-1 gd_barnes
565*2^1269153-1 gd_barnes
433*2^1259831-1 gd_barnes
423*2^1243214-1 gd_barnes
425*2^1240016-1 gd_barnes
595*2^1234025-1 gd_barnes
569*2^1232424-1 gd_barnes
513*2^1229391-1 henryzz
593*2^1227476-1 gd_barnes
573*2^1226854-1 gd_barnes
563*2^1216134-1 gd_barnes
429*2^1205440-1 gd_barnes
475*2^1204215-1 gd_barnes
469*2^1200635-1 gd_barnes
507*2^1192088-1 gd_barnes
519*2^1190660-1 gd_barnes
481*2^1182519-1 gd_barnes
505*2^1165307-1 odicin
417*2^1155458-1 Lennart
571*2^1154111-1 Lennart
461*2^1150934-1 Lennart
565*2^1148579-1 Lennart
531*2^1146439-1 Lennart
413*2^1144580-1 Lennart
453*2^1144428-1 Lennart
553*2^1143639-1 Lennart
583*2^1137603-1 Lennart
583*2^1128879-1 juhehe
573*2^1128632-1 henryzz
507*2^1127304-1 juhehe
469*2^1105345-1 vaughan
573*2^1101398-1 vaughan
451*2^1096999-1 vaughan
503*2^1092022-1 vaughan
475*2^1089627-1 vaughan
569*2^1079392-1 Sashixi
435*2^1077677-1 odicin
503*2^1070448-1 mdettweiler
473*2^1063908-1 Sashixi
549*2^1063317-1 Sashixi
523*2^1062947-1 mdettweiler
511*2^1055989-1 Sashixi
525*2^1053162-1 mdettweiler
511*2^1051499-1 Sashixi
489*2^1041511-1 Flatlander
593*2^1040744-1 Flatlander
573*2^1039963-1 Flatlander
513*2^1038382-1 Flatlander
453*2^1036971-1 Flatlander
581*2^1035962-1 Flatlander
531*2^1031987-1 mdettweiler
555*2^1029045-1 odicin
411*2^1025451-1 Flatlander
407*2^1025072-1 Flatlander
437*2^1023678-1 Flatlander
441*2^1021669-1 Flatlander
549*2^1021391-1 Flatlander
471*2^1017306-1 Flatlander
425*2^1016928-1 odicin
585*2^1016441-1 odicin
469*2^1012299-1 Flatlander
513*2^1011678-1 Flatlander
497*2^1000426-1 Lennart
[/code][FONT=Verdana][COLOR=black]Primes confirmed from drive #13:[/COLOR][/FONT]
[code]
Prime found by
405*2^1508592-1 Mini-Geek
405*2^1399165-1 gd_barnes
405*2^1146533-1 Lennart
443*2^1143154-1 Lennart
405*2^1133886-1 henryzz
[/code][COLOR=black][FONT=Verdana]Status:[/FONT][/COLOR]
[code]
n-range tested by Status # primes
1600.0K-1700.0K PRPnet (G9000) in progress 4
1500.0K-1600.0K PRPnet (G9000) complete 16 (plus 1 confirmed)
1400.0K-1500.0K PRPnet (G9000) complete 23
1300.0K-1400.0K PRPnet (G9000) complete 13 (plus 1 confirmed)
1200.0K-1300.0K PRPnet (G9000) complete 20
1100.0K-1200.0K PRPnet (G9000) complete 18 (plus 3 confirmed)
1050.0K-1100.0K PRPnet (G9000) complete 12
1035.0K-1050.0K LLRnet (G3000) complete 6
1025.0K-1035.0K PRPnet (G9000) complete 4
1020.0K-1025.0K LLRnet (G3000) complete 3
1000.0K-1020.0K PRPnet (G9000) complete 6
[/code]All remaining known primes for this drive as of 2021/02/07:
[code]
435*2^1853363-1
[/code]All of the primes found in this range will be over 300,000 digits, and will grow steadily in size as the drive progresses. As of this writing, primes of this size come in within the top 1000 largest known primes! This drive, with its potential to produce quite a number of megabit primes, should prove most interesting. :popcorn:

Max :smile:

I've included the Team Drive #13 page, updated the NPLB Team Drives Summary page and reserved all k-values for this drive on the 300<k<2000 page.

[QUOTE]server = "www.noprimeleftbehind.net"
port = 3000[/QUOTE]
is dry?

[QUOTE=Flatlander;268383]is dry?[/QUOTE]
Ah yes, I have been a little lax in my duties there...I really should have gotten that loaded shortly after I posted this thread :ermm:

Reserving 1020K-1025K for port 3000. :smile:

Edit: Loaded, server is up now. Come and get it! :grin:

Thanks Max. :smile:

Reserving 1025K-1035K for port 9000.

Per a PM exchange, c10ck3r is reserving n=1035K-1036K. I sent him the file.

Reserving n=1036K-1040K for port 3000.

[QUOTE=gd_barnes;269764]Per a PM exchange, c10ck3r is reserving n=1035K-1036K. I sent him the file.[/QUOTE]

C10ck3r is releasing n=1035K-1036K.

Max, can you load this range at the beginning of the knpairs file for port 3000? Thanks.

[QUOTE=gd_barnes;270672]C10ck3r is releasing n=1035K-1036K.

Max, can you load this range at the beginning of the knpairs file for port 3000? Thanks.[/QUOTE]
Done. :smile:

Reserving n=1040K-1050K for port 3000.

Reserving 1050K-1055K for port 9000.

Reserving 1055K-1060K for port 9000.

Reserving 1060K-1065K for port 9000.

Reserving 1065K-1070K for port 9000.

Reserving n=1070K-1080K for port 9000.

Reserving n=1080K-1100K for port 9000.

Reserving n=1100K-1120K for port 9000.

Reserving n=1120K-1140K for port 9000.

Reserving n=1140K-1160K for port 9000.

1000K-1100K has been completed by LLRnet port 3000 and PRPnet port 9000; processed results have been emailed to Gary.

The port 9000 status pages should load a lot faster now--the server's database has been significantly lightened with the removal of this range and, particularly, a huge chunk of the 7th Drive that had been sitting in there for over a year. I'll be similarly processing and cleaning out port 2000 next, and then will upgrade both servers to the latest prpserver version 5.0.8.

I just optimized the database tables for that port now the range is removed.
should be a touch quicker.

[QUOTE=AMDave;310020]I just optimized the database tables for that port now the range is removed.
should be a touch quicker.[/QUOTE]
Excellent, thanks! (Wow, it loads fast--I just pulled up [url]http://noprimeleftbehind.net:9000/all.html[/url] in half a second flat! :w00t:)

BTW, how does one go about optimizing the tables (what commands, etc.)? You've probably told me before but I can't recall it for the life of me... :rolleyes:

email sent

[QUOTE=AMDave;310068]email sent[/QUOTE]
I am afraid max isn't the only one interested. Am I right in thinking that optimising the tables after adding a rediculous amount of candidates is just as helpful as doing it after deleting them? I created a server recently with too many candidates and it took ages to respond to the client.

Similar request for info. I started my personal server with ~1000 k's at n = 2500, originally loaded with a bit over a million candidate tests. I've gotten it down to 500,000 due to a lot of messy SQL (and completing tests / finding primes), but it would be awesome to get some better code. Of course, next time I'll narrow things down a bit more first.

[QUOTE=CGKIII;310112]Similar request for info. I started my personal server with ~1000 k's at n = 2500, originally loaded with a bit over a million candidate tests. I've gotten it down to 500,000 due to a lot of messy SQL (and completing tests / finding primes), but it would be awesome to get some better code. Of course, next time I'll narrow things down a bit more first.[/QUOTE]
It turns out it's pretty simple: just run "optimize table [I]table[/I];" for each table in the database. (I'm assuming you already know the basics of getting in and navigating through an SQL database, since you were able to clean out old tests from your server.)

Is there any particular reason why drive 13 is so far behind drive 14 even though it is easier and has lower ks?

[QUOTE=henryzz;312069]Is there any particular reason why drive 13 is so far behind drive 14 even though it is easier and has lower ks?[/QUOTE]

Because there's more activity on Drive 14 (Port 2000) than on Drive 13 (Port 9000):

the last days there were ~300 paris done on Port 2000 but only ~30 on Port 9000.
End of August the difference in pairs was much higher.

[QUOTE=henryzz;312069]Is there any particular reason why drive 13 is so far behind drive 14 even though it is easier and has lower ks?[/QUOTE]

We had two rallies on drive 14 when it was behind drive 13. Then a big cruncher stayed on drive 14 for a long time afterwords. Our next rally will be on drive 13.

Reserving n=1160K-1200K for port 9000.

I seem to be searching all the primeless ranges on this drive so that everyone else can find the primes. :no: There's been one prime in the last n=23K range; by far the worst range since the drive started. I wonder if all of my machines have gone bad at once.

[QUOTE] There's been one prime in the last n=23K range; by far the worst range since the drive started.[/QUOTE]Probably setting up for a nice run shortly.

[QUOTE=gd_barnes;335562]I seem to be searching all the primeless ranges on this drive so that everyone else can find the primes. :no: There's been one prime in the last n=23K range; by far the worst range since the drive started. I wonder if all of my machines have gone bad at once.[/QUOTE]
Must be because I started crunching there on 2 cores...my luck's been pretty poor on this server, with 15704 tests (approx 1.5-2 primes expected; most of those tests were long ago when the numbers were smaller) and 0 primes.
[QUOTE=MyDogBuster;335565]Probably setting up for a nice run shortly.[/QUOTE]
I'd like to think so, but that's a good example of gambler's fallacy. Crunching primes in NPLB, CRUS, etc. has taught me a great deal about probability and randomness: expect the unexpected. But don't be surprised when it plays out as the most likely scenario, either. And if you ever think you know what's going to happen based on past random events, you're (probably) wrong.

I have confirmed that 405*2^1508592-1 is prime. I tried to submit it to the Top 5k before I realized it was already known. :blush: