PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
1) Message boards : Number crunching : Tour de Primes 2021 (Message 147682)
Posted 8 hours ago by Profile Michael GoetzProject donor
As we've done for the last couple of years, there will also be a "just for giggles" Double Checker scoreboard at http://www.primegrid.com/challenge/tdp_2021_dc.php.

This is also affected by the fast double checks introduced by LLR2. I suppose LLR2 primes have no official DC users, and this may make the tdp_2021_dc stats hard to compare to the "real" stats. /JeppeSN


This is correct. All LLR projects eligible for TdP, except for PPSE, do not have double checkers, so the 2nd place page will only have PPSE and GFN primes.
2) Message boards : Number crunching : Tour de Primes 2021 (Message 147668)
Posted 20 hours ago by Profile Michael GoetzProject donor
Tour de Primes 2021

Welcome to the 13th annual Tour de Primes. 2 is the first prime number...and the only even one. This makes it unique among prime numbers. Therefore, February is declared Prime month...being the 2nd month of the year. :) And there's no better way to pay homage to a prime number than to go out and find one. :) More precisely, a Top 5000 prime.

For the month of February, an informal competition is offered. There are no challenge points to be gained... just a simple rare jersey at the end of the month to add to your badge list. No pressure or stress other than what you put on yourself. :)

For 2021, we're bringing back the badges introduced in 2018:


  • Red Jersey -- discoverer of largest prime
  • Yellow Jersey -- prime count leader (tiebreaker will be prime score)
  • Green Jersey -- points (prime score) leader
  • Polk-a-dot Jersey -- on the 19th of February we'll have a "Mountain Stage" and award the Polk-a-dot Jersey to the one who finds the most primes on that day (tiebreaker will be prime score for that day).
  • Prime badge -- awarded to everyone who finds an eligible prime during the month of February. This is a counter badge, so if you find more than one prime it will show how many you've found, up to 99.
  • Mega prime badge -- awarded to everyone who finds a mega prime during February. This is a counter badge.
  • Mountain Stage prime badge -- awarded to everyone who finds an eligible prime during the Mountain Stage. This is a counter badge.
  • Mountain Stage mega prime badge -- awarded to everyone who finds a mega prime during the Mountain Stage. This is a counter badge.



Results will be available at http://www.primegrid.com/challenge/tdp_2021.php.

As we've done for the last couple of years, there will also be a "just for giggles" Double Checker scoreboard at http://www.primegrid.com/challenge/tdp_2021_dc.php.

As with the last few years, for all primes (BOINC and PRPNet) we're using the new reporting system whereby the prime's date of discovery determines whether it's eligible for the Tour de Primes. Prior to 2014, the date of verification for BOINC primes was used while the discovery date was used for PRPNet primes. The current system is more intuitive and fairer.

Note that SGS-LLR and GFN-15 are too small to be reported to the Top 5000 primes list and are therefore not eligible for the 2021 Tour de Primes.

Currently, the fastest opportunities to find Top 5000 primes is with the PPSE (LLR), and GFN-16 (65536) projects. Of course, should someone find a prime in the mega-prime searches, this would certainly give them a good shot at the green or red jerseys. Not a guarantee, however, as in 2020 there were 44 mega primes found in the Tour de Primes. Overall, in 2020 we averaged over three mega primes per week for the entire year, so you might need more than "merely" a mega prime to take home green.

All ports in PRPNet are available for the competition.

To participate in BOINC PPSE (LLR), GFN-16, or any other eligible LLR or Genefer project, all you have to do is select it in your PrimeGrid preferences. AP27 sequences are not reportable at T5K, so are not eligible for Tour de Primes. WW primes are also not reportable to T5K.

Sieve projects don't find primes, so PPS-Sieve can't find anything in TdP.

Good Luck, have fun, and enjoy! :D

Previous Winners

- tng*
- RFGuy_KCCO
- Scott Brown
- mattozan

- Honza
- Scott Brown
- 288larsson
- [AF>EDLS]GuL

- Robish
- [AF>Amis des Lapins] dthonon
- [AF>Amis des Lapins] dthonon
- tng*

- wdethomas
- tng*
- wdethomas
- tng*

- boss
- Scott Brown
- boss
- Orange_1050

- Scott Brown
- Randall J. Scalise
- vmc

- [DPC]x-RaY99_the_one_man_team
- [DPC]x-RaY99_the_one_man_team
- Lonnie Christensen

- [DPC]x-RaY99_the_one_man_team
- [DPC]x-RaY99_the_one_man_team
- PBT_marian_boss

- Scott Brown
- Usucapio Libertatis
- Scott Brown

- shanky123
- [BOINCstats] LostBoy
- Snf*

- lennart
- lennart
- [SG]marodeur6

- lennart
- s-yama
- lennart

Full rankings can be seen here: 2009 | 2010 | 2011 | 2012 | 2013 | 2014 | 2015 | 2016 | 2017 | 2018 | 2019 | 2020

Totals by Year

    2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 Total Primes found 212 309 766 646 238 254 254 346 246 256 277 377 Total Score 457.30 2663.27 21803.72 20727.04 15614.83 20982.77 30268.46 43656.50 40201.94 55393.50 63588.96 130171.15




Tips and Strategies:

Tip #1: He (or she) who finds the prime FIRST is the discover of the prime. It's a competition between you and your wingman. While having a fast computer helps, your computer is only useful when it's running a task. If you have a cache of tasks sitting on your computer waiting to run, chances are your wingman will return the task before you've even started it. Setting both BOINC cache settings to "0 days" is strongly recommended. People with slow computers find primes all the time because their wingman downloaded the task yesterday but won't start running it until tomorrow. Set your cache to 0 days!

If you're going to ignore tip #1, don't even bother reading the rest. Seriously.

Tips for LLR:


  • Your mileage may vary. What works for me may not work for you. Before TdP 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. (But see below for exceptions.)

    • 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.


  • Use LLR's multithreaded mode. It requires a little bit of setup, but it's worth the effort. Follow these steps:

    • Use multi-threading on larger tasks. What constitutes "larger" varies according to how fast your CPU is and your personal tastes.
    • It's no longer necessary to use app_config.xml to set up multi-threading. On the PrimeGrid preferences page, set "Multi-threading: Max # of threads for each task" to "No limit" to use the maximum number of threads for each task, or select a specific thread count if you prefer.


Tips for GFN:


  • Only run GFN on a GPU. Use your CPU for LLR tasks where it will be much more efficient.
  • Unless you have a really slow GPU and a really fast CPU, leave a CPU core free to service the GPU. You'll want the more powerful GPU running at full speed, even if it slows down the CPU somewhat. A hyperthread should be sufficient if your CPU supports hyperthreading. For example, on a 4 core CPU (without hyperthreading), you could set BOINC to "use 75% of the CPUs" to reserve one core for the GPU.

3) Message boards : Number crunching : New warnings when LLR2 detects Gerbicz errors (Message 147552)
Posted 5 days ago by Profile Michael GoetzProject donor
There is an opportunity suggested here to create a tool that is very sensitive to computer stability. During the run-up to the current challenge, I noticed these "Gerbicz errors" in one of the output logs on a Ryzen 3700X, while testing an offline WU, but only with certain task/thread combinations, notably 8 tasks of 2 threads. The problem is yet unresolved, but for now running 8 tasks/1 thread works, and also provides slightly higher throughput. So even though this PC is not overclocked, and can run Memtest all night with no errors, it has a problem!


Many of us have noticed that at least some Ryzens are not the most stable of CPUs. I've not only turned off Boost on my 3700X, but also turned off the XMP setting on the memory, which lowers it to stock speeds.
4) Message boards : General discussion : Suggestion: Team name in team 'info page' (Message 147514)
Posted 7 days ago by Profile Michael GoetzProject donor
Name on browser tab only


That's where it is.
5) Message boards : General discussion : Suggestion: Team name in team 'info page' (Message 147510)
Posted 7 days ago by Profile Michael GoetzProject donor
The name is already there. :)

Granted, it's not in the most obvious place, but it *is* there. I'll give you a little time to find it on your own. :P

6) Message boards : Generalized Fermat Prime Search : Guessing the future of GFN-22 and DYFL (Message 147370)
Posted 14 days ago by Profile Michael GoetzProject donor
Now I'm asking once again: what are runtimes of real GFN-22/DYFL tasks on your GPUs? When I'll know runtimes, I can calculate how efficient sieve will be and how far it should go to stay efficient in your setup.

The last line of his latest post may mean that the Genefer runtime is about a day. /JeppeSN


Need to know *which* GFN you're talking about. DYFL uses a slower transform than GFN-22, so it takes about 25% longer to run.
7) Message boards : Problems and Help : Can't figure out why CPU isn't being used 100% (Message 147348)
Posted 15 days ago by Profile Michael GoetzProject donor
That means you shouldn't run more than 1 MEGA with 4 threads (CPUs),
or 2 MEGAs with 2 threads (CPUs) each. By doing this, your CPUs will be
close to 100% and you'll do at least twice as many MEGA tasks per day.

Since you're running other things (which use L3 too), I'd recommend 1 MEGA with 4 threads.
If you weren't running other things, 2 MEGAs with 2 threads might be slightly faster.


While this is generally good advice for most other CPU apps, I don't believe GFN supports multithreading (except for GFN-21).


He is running PPS-MEGA on the CPU.
8) Message boards : Problems and Help : Can't figure out why CPU isn't being used 100% (Message 147347)
Posted 15 days ago by Profile Michael GoetzProject donor
Each MEGA task uses 2 MB L3 cache. Since you're running 4 MEGA tasks, that's 8 MB of L3 demand.
You only have 6 MB of L3 available. You're thrashing your L3 cache. That means every MEGA
memory access has to wait for a read of RAM memory (very slow vs. L3 cache).
Your MEGA data never has a chance to be reused from L3 cache before
it's knocked out of L3 cache by another MEGA data access.

That means you shouldn't run more than 1 MEGA with 4 threads (CPUs),
or 2 MEGAs with 2 threads (CPUs) each. By doing this, your CPUs will be
close to 100% and you'll do at least twice as many MEGA tasks per day.

Since you're running other things (which use L3 too), I'd recommend 1 MEGA with 4 threads.
If you weren't running other things, 2 MEGAs with 2 threads might be slightly faster.


This is all true, but it is off-topic and doesn’t answer his question. Cache misses are too low level a concept to be reflected in the Windows Task Manager. It does not explain why he’s seeing only 50% utilization.

TThrottle and similar utilities/tools/features could cause this, however. A clue here is the very low clock speed. The device is likely overheating, and something may be idling the CPU in order to keep the temperature down.
9) Message boards : Wieferich and Wall-Sun-Sun Prime Search : WW 1.05 credits (Message 147298)
Posted 17 days ago by Profile Michael GoetzProject donor
Are you looking at this computer? that's the one I tested on?

But why WW is 25% faster on one of the two RTX 2070?
RTX 2070, driver 432.00, i7-6700K, Win10: 91M primes per second WW + Cullen (4 threads / 4 cores, L3: 8MB, HT off) RTX 2070, driver 441.08, i7-9700K, Win10: 114M primes per second WW + 2 * Cullen (2 * 4 threads / 8 cores, L3: 12MB)
The driver (I don't think so), HT on could help on the 6700, but it does not give an explanation.

There seems to be a big variation in a number of TNG's gpus - some of the 2070 supers are running even slower than the above. Is there a cooling problem resulting in downclocking?



1) Different clocks... (clocks are visible in the work unit outputs for the GFN work done on these).

2) Dual GPU systems only report the device -0 type. Some of tng's dual GPU machines have a 2070 with a 2070 super.


Well it's all very confusing.
this pc reports as a 2070 super but the tasks identify as a 2080 and yet they're running 800-1600s/task.

this one reports as a 2070 super but has tasks running as 2070s + 2080 and both running 500-700s/task.




If there's more than one GPU, and the task is paused and resumed, it may resume on a different GPU. Pretty much, all bets are off in a multi-GPU system with heterogeneous GPUs.
10) Message boards : Number crunching : Great Conjunction Challenge (Message 147215)
Posted 19 days ago by Profile Michael GoetzProject donor
A few days ago, GFN-19 was calculated with OCL3 in approx. 50 minutes (using GTX 1660 Super).
Today, GFN-19 was calculated with OCL2 and it took more than 1h 20m.
Is it going to stay like this?


Yes.

GFN-19 recently passed the OCL3 limit, and now must use OCL2 going forward. Unless you get a resend of an older GFN19, everything will be on OCL2 from now on.


Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2021 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 4.23, 4.00, 4.11
Generated 19 Jan 2021 | 21:16:06 UTC