PrimeGrid
Please visit donation page to help the project cover running costs for this month
1) Message boards : Wieferich and Wall-Sun-Sun Prime Search : Ratio between near-WW primes (Message 156536)
Posted 22 days ago by GDB
So, the "∞" in the B column for WW on the home page, isn't really true?
2) Message boards : Number crunching : Pi Approximation Day Challenge (Message 156423)
Posted 26 days ago by GDB
54
3) Message boards : Number crunching : Way too much work (Message 156110)
Posted 48 days ago by GDB
NEVER (or rarely) use "NO LIMIT" for maximum # of simultaneous tasks.
Always set it to a reasonable number for the task queue you want.
It's easy to change, and it's better than downloading hundreds of tasks you don't want.
4) Message boards : Number crunching : Can I dictate number of CPU & GPU jobs? (Message 156109)
Posted 48 days ago by GDB
ps: I never use "NO LIMIT" (or rarely) for maximum # of simultaneous tasks. ALWAYS use a number reasonable for the type of tasks you are running.
5) Message boards : Number crunching : Can I dictate number of CPU & GPU jobs? (Message 156108)
Posted 48 days ago by GDB
The way I manage CPU/GPU load is to NEVER select both at the same time.

First, determine and select the CPU/GPU subtasks you want to run.

Determine whether CPU or GPU tasks run longer.

Select the longer running CPU/GPU type ONLY and download a queue for a couple of days running or enough tasks so they don't expire before they run.

Select ONLY the shorter CPU/GPU type and expand the number of tasks for the number of shorter running tasks you want running.

Then just leave it alone. As the shorter CPU/GPU tasks finish, more will be downloaded automatically to run.

Only when the queue of longer running CPU/GPU tasks is close to empty do I select ONLY the longer CPU/GPU type and rebuild the queue for that type, and then reselect the shorter CPU/GPU type again.

6) Message boards : Number crunching : Strange timings on AMD 3700X (Message 156004)
Posted 59 days ago by GDB
A few of the cores may be faster because they are able to keep all of their data in L3 cache.
Everybody else has to access slow main memory. Life isn't fair. First come, first served.
7) Message boards : Number crunching : Strange timings on AMD 3700X (Message 156001)
Posted 59 days ago by GDB
It seems that when you have more than 4 workers, your L3 cache usage has exceeded your 32 MB of L3 cache.
So your 8 workers are causing the memory subsystem to thrash and all memory requests are going to slow memory, instead of fast L3 cache.
8) Message boards : Proth Prime Search : PPSE (Proth Prime Search Extended) too small for Top 5000 now (Message 155447)
Posted 94 days ago by GDB
Assuming PPSE gains 188 digits per week on average on the trailing edge of T5k, it will catch up on August 4th.

Please note this is a very rough guesstimate.
I will include an adjusted ETA in the next update next saturday.


Don't forget there are 3 challenges between now and Sept. Each of those will likely reduce PPSE tasks, and find primes that will increase the T5K base.
9) Message boards : Proth Prime Search : PPSE (Proth Prime Search Extended) too small for Top 5000 now (Message 155435)
Posted 95 days ago by GDB
With PPSE on LLR2, I decided to push there and started wondering when will PPSE rejoin Top5k.

With current performance (and thanks for LLR2), PPSE is advancing almost 1k in digits every 10 days.
That is esential, because 508400 digits is still shy of current 511k digits trailing edge of T5K.

While there are about 40 PPSE primes in last two weeks (and advancing toward T5K), it also slips away because of other/larger primes being reported.
~10 MEGA + 15 GFN16 primes that are larger than PPSE + a bit more from non-PG primes.
In order for PPSE to reach and STAY in T5K, there need to be more PPSE primes than others.
Also, PPSE needs to advance faster than trailing edge.

If we keep the pace, 2 weeks are 1k digits, which is about 50 places on T5K trailing edge.

GFN-19 challenge will probably postpone this effort but it may happend in early June I guess...


From the latest stats, it looks to be closer to Sept. than June before PPSE rejoins T5K list.
10) Message boards : Number crunching : Credit Milestones (Message 154823)
Posted 159 days ago by GDB
3 G for GDB


Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2022 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 0.26, 0.73, 0.88
Generated 18 Aug 2022 | 10:34:30 UTC