PrimeGrid: 50 years First ARPANET Connection Challenge

[gemini8]

Erstmal die Einladung wie bei PrimeGrid zu finden. Muß leider zur Arbeit. Meine Version folgt also später.

Welcome to the 50 years First ARPANET Connection Challenge

Arpanet carried its first message on October 29, 1969, laying the foundation for today’s networked world. Fifty years later, more than 4 billion people have internet access, and the number of devices connected to IP networks is more than double the global population. The name Arpanet came from the U.S. military arm that funded it, the Advanced Research Projects Agency. When Arpanet was created, it connected five sites: UCLA, Stanford, UC Santa Barbara, the University of Utah and BBN Technologies.

The first Arpanet node was set up at UCLA on Aug. 30, 1969. The second node, at the Stanford Research Institute, was set up on Oct. 1. The first data message sent between the two networked computers occurred on Oct. 29, when UCLA computer science professor Leonard Kleinrock sent a message from his school's host computer to another computer at Stanford. Kleinrock intended to write "login" to start up a remote time-sharing system, but the system crashed after only two letters, "l" and "o", were transmitted.

In 1983, the U.S. Defense Department spun-off MILNET, which was the part of Arpanet that carried unclassified military communications. (MILNET was later renamed the Defense Data Network and finally NIPRNET, for Non-classified IP Router Network.) Arpanet was renamed the internet in 1984, when it linked 1,000 hosts at university and corporate labs.

The eighth Challenge of the 2019 Challenge series is a 5 day challenge celebrating 50 years since the first ARPANET Connection. The challenge is being offered on the 321 Prime Search (LLR) application.

To participate in the Challenge, please select only the 321 Prime Search LLR (321) project in your PrimeGrid preferences section. The challenge will begin 24th October 2019 00:00 UTC and end 29th October 2019 00:00 UTC.

Application builds are available for Linux 32 and 64 bit, Windows 32 and 64 bit and MacIntel. Intel CPUs with FMA3 capabilities (Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake) will have a very large advantage, and Intel CPUs with dual AVX-512 (certain recent Intel Skylake-X and Xeon CPUs) will be the fastest.

ATTENTION: The primality program LLR is CPU intensive; so, it is vital to have a stable system with good cooling. It does not tolerate "even the slightest of errors." Please see this post for more details on how you can "stress test" your computer. Tasks on one CPU core will take 12 hours on fast/newer computers and 2 days+ on slower/older computers. If your computer is highly overclocked, please consider "stress testing" it. Sieving is an excellent alternative for computers that are not able to LLR.

Highly overclocked Haswell, Broadwell, Skylake, Kaby Lake or Coffee Lake (i.e., Intel Core i7, i5, and i3 -4xxx or better) computers running the application will see fastest times. Note that PPS-DIV is running the latest AVX-512 version of LLR which takes full advantage of the features of these newer CPUs. It's faster than the previous LLR app and draws more power and produces more heat. If you have certain recent Intel Skylake-X and Xeon CPUs, especially if it's overclocked or has overclocked memory, and haven't run the new AVX-512 LLR before, we strongly suggest running it before the challenge while you are monitoring the temperatures.

Please, please, please make sure your machines are up to the task.

Multi-threading optimisation instructions

Those looking to maximise their computer's performance during this challenge, or when running LLR in general, may find this information useful.

• * Your mileage may vary. Before the challenge starts, take some time and experiment and see what works best on your computer.
  * If you have an Intel CPU with hyperthreading, either turn off the hyperthreading in the BIOS, or set BOINC to use 50% of the processors.
  • *If you're using a GPU for other tasks, it may be beneficial to leave hyperthreading on in the BIOS and instead tell BOINC to use 50% of the CPU's. This will allow one of the hyperthreads to service the GPU.
  * The new multi-threading system is now live. This will allow you to select multi-threading from the project preferences web page. No more app_config.xml. It works like this:
  • * In the preferences selection, there are selections for "max jobs" and "max cpus", similar to the settings in app_config.
    * Unlike app_config, these two settings apply to ALL apps. You can't chose 1 thread for SGS and 4 for SoB. When you change apps, you need to change your multithreading settings if you want to run a different number of threads.
    * There will be individual settings for each venue (location).
    * This will eliminate the problem of BOINC downloading 1 task for every core.
    * The hyperthreading control isn't possible at this time.
    * The "max cpus" control will only apply to LLR apps. The "max jobs" control applies to all apps.
  * If you want to continue to use app_config.xml for LLR tasks, you need to change it if you want it to work. Please see this message for more information.
  * Some people have observed that when using multithreaded LLR, hyperthreading is actually beneficial. We encourage you to experiment and see what works best for you.

Time zone converter:

The World Clock - Time Zone Converter

NOTE: The countdown clock on the front page uses the host computer time. Therefore, if your computer time is off, so will the countdown clock. For precise timing, use the UTC Time in the data section at the very top, above the countdown clock.

Scoring Information

Scores will be kept for individuals and teams. Only tasks issued AFTER 24th October 2019 00:00 UTC and received BEFORE 29th October 2019 00:00 UTC will be considered for challenge credit. We will be using the same scoring method as we currently use for BOINC credits. A quorum of 2 is NOT needed to award Challenge score - i.e. no double checker. Therefore, each returned result will earn a Challenge score. Please note that if the result is eventually declared invalid, the score will be removed.


At the Conclusion of the Challenge

• We kindly ask users "moving on" to ABORT their tasks instead of DETACHING, RESETTING, or PAUSING.
  
  ABORTING tasks allows them to be recycled immediately; thus a much faster "clean up" to the end of an LLR Challenge. DETACHING, RESETTING, and PAUSING tasks causes them to remain in limbo until they EXPIRE. Therefore, we must wait until tasks expire to send them out to be completed.
  
  Please consider either completing what's in the queue or ABORTING them. Thank you.

About 321 Search

321 Search began in February 2003 from a post by Paul Underwood seeking help from interested parties in a prime search attempt of the form 3*2^n-1. The initial goal was to build upon the completed work at Proth Search and extend the list of known primes to an exponent of 1 million (n=1M). That was quickly achieved so they advanced their goal to finding a mega prime for which they sieved up to n=5M.

As seen on PrimeGrid's front page, that goal was achieved on 23 Mar 2008, 7:57:28 UTC, when Dylan Bennett of Canada returned a positive result for n=4235414 (3*2^4235414-1). official announcement | decimal representation

PrimeGrid added the +1 form and continues the search up to n=25M.

Primes known for 3*2^n+1 occur at the following n (PrimeGrid's finds in bold & linked):
1, 2, 5, 6, 8, 12, 18, 30, 36, 41, 66, 189, 201, 209, 276, 353, 408, 438, 534, 2208, 2816, 3168, 3189, 3912, 20909, 34350, 42294, 42665, 44685, 48150, 54792, 55182, 59973, 80190, 157169, 213321, 303093, 362765, 382449, 709968, 801978, 916773, 1832496, 2145353, 2291610, 2478785, 5082306, 7033641, 10829346

Primes known for 3*2^n-1 occur at the following n (PrimeGrid's finds in bold & linked):
1, 2, 3, 4, 6, 7, 11, 18, 34, 38, 43, 55, 64, 76, 94, 103, 143, 206, 216, 306, 324, 391, 458, 470, 827, 1274, 3276, 4204, 5134, 7559, 12676, 14898, 18123, 18819, 25690, 26459, 41628, 51387, 71783, 80330, 85687, 88171, 97063, 123630, 155930, 164987, 234760, 414840, 584995, 702038, 727699, 992700, 1201046, 1232255, 2312734, 3136255, 4235414, 6090515, 11484018, 11731850, 11895718

What is LLR?

The Lucas-Lehmer-Riesel (LLR) test is a primality test for numbers of the form N = k*2^n − 1, with 2^n > k. Also, LLR is a program developed by Jean Penne that can run the LLR-tests. It includes the Proth test to perform +1 tests and PRP to test non base 2 numbers. See also:

• *Lucas-Lehmer-Riesel test (WIKI)
  *Download LLR by Jean Penné

(Edouard Lucas: 1842-1891, Derrick H. Lehmer: 1905-1991, Hans Riesel: 1929-2014).

[gemini8]

Erstmal die Einladung wie bei PrimeGrid zu finden. Muß leider zur Arbeit. Meine Version folgt also später.

Ich kann natürlich jetzt schon sagen, daß ich mitspielen werde.

[Yeti]

Wenn ich das richtig sehe, wieder ein CPU-Race, dann also ohne mich

Allen, die teilnehmen werden, wünsche ich viel Spaß und gutes Gelingen

[Frank [RKN]]

Wenn ich das richtig sehe, wieder ein CPU-Race, dann also ohne mich

Hallo Yeti, schön dich mal wieder zu lesen. Auch wenn es nur eine Absage ist

Dafür darfst du deine RTX-Karten jetzt bei GPUGrid voll ausfahren

[Yeti]

Dafür darfst du deine RTX-Karten jetzt bei GPUGrid voll ausfahren

Bist du sicher? Ich finde bei denen nix, daß das Problem mit den RTX-Karten zwischenzeitlich gelöst sei

[gemini8]

Dafür darfst du deine RTX-Karten jetzt bei GPUGrid voll ausfahren

...und ich wollte ihn heimlich überholen...

[Frank [RKN]]

Bist du sicher? Ich finde bei denen nix, daß das Problem mit den RTX-Karten zwischenzeitlich gelöst sei

Dann schau doch erstmal bei uns im Forum nach

@Jens : Knapp 22 Mio, das schaffst du bis Yeti alle Rechner an den Start gebracht hat

[Yeti]

Bist du sicher? Ich finde bei denen nix, daß das Problem mit den RTX-Karten zwischenzeitlich gelöst sei

Dann schau doch erstmal bei uns im Forum nach

Äh, ja, danke

Hab es bei GPUGrid in den FAQs auch gefunden anstatt in den News

@Jens : Knapp 22 Mio, das schaffst du bis Yeti alle Rechner an den Start gebracht hat

HM, da GPUGrid zur Zeit keine WUs zu haben scheint sieht es wohl schlecht aus

[Michael H.W. Weber]

Ich werde beim Primegrid-Race auch wieder mitrechnen.
Allerdings habe ich seit der projektseitigen Änderungen mit den MT-Einstellungen echten Ärger mit dem Projekt: Es laufen z.B. bei den beiden Sieve-Subprojekten plötzlich Zombie-Tasks, wenn man MT auf maximal einstellt (und die Projekte anscheinend MT gar nicht können (was mir ebenfalls neu ist) und also für 4 CPUs auch 4 Tasks laden). Abgesehen davon bringen die Sieve-Tasks nicht mehr wie früher deutlich mehr Credits - also "bullshit", die noch zu rechnen.
Ich hoffe mal, dass man ohne .xml das kommende Race-Subprojekt auch im MT Mode rechnen kann, sonst wird es extrem albern bei den Laufzeiten...

Michael.

[gemini8]

Kombi app_config plus Einstellungen bei PrimeGrid sind top, wenn man sauber arbeitet.

[Reddogg]

Werde diesmal net dabei sein. Mein Rechner läuft aktuell für WCG. CPU-Tasks sind so eine Sache.

[compalex]

bin dabei

gemini8, packst du diesmal den cluster?