Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
1)
Message boards :
321 Prime Search :
321 Sieve is being SUSPENDED
(Message 143721)
Posted 983 days ago by  Myrskylyhty
Maybe when us youngsters are at a retirement home, we'll start up 321 sieve for 50M-100M.
|
2)
Message boards :
Number crunching :
Badges III
(Message 139090)
Posted 1171 days ago by Myrskylyhty
Finally! 321 is a blast!
|
3)
Message boards :
Proth Prime Search :
PPS-MEGA: Smaller FFT longer crunch time ?
(Message 138158)
Posted 1201 days ago by Myrskylyhty
With my 9900KS, the 240K FFT length PPS Mega tasks take over 2x longer than the 256K FFT length tasks. Even DIV tasks are faster than the 240K FFT length PPS Mega.
What's even more weird: trying to run any current length PPS Mega task using the independant LLR app in command line, every single task runs with 256K FFT length.
Could something cause the Boinc LLR-app to occasionally run using a "wrong" FFT length?
|
4)
Message boards :
Number crunching :
Tour de Primes 2020
(Message 137827)
Posted 1210 days ago by Myrskylyhty
Just a note to people: Even if your 1st % goes up by multithreading, your 1st task rate might not necessarily go up.
For example, a 9900KS will go through 30 % more tasks if single-coring PPSE rather than two-coring. That means if I wanted to use two cores per tasks, my 1st percentage would have to go up over 30 % to offset the difference.
In addition there is the fact that the first option is processing 30 % more candidates, thus advancing our work as a Primegrid collective much more! So if you're breaking even, please use the more productive option.
I think people are a bit blinded by just the 1st percentage rather than looking at the 1st tasks per day. It is a bit of a silly situation if everyone just gives up 30 % of their computing power while the effective prime finder chance stays the same.
Play it smart everyone! :)
|
5)
Message boards :
Storm message board
(Message 135446)
Posted 1276 days ago by Myrskylyhty
Sorry, dthonon ;P
https://stats.free-dc.org/subproj/pgrid/321_LLR
gleefullme, you're next!
|
6)
Message boards :
Number crunching :
Transit of Mercury Across the Sun Challenge
(Message 134773)
Posted 1304 days ago by Myrskylyhty
It's the last day! There's less than 21 hours remaining.
Challenge: Transit of Mercury Across the Sun
App: 8 (PSP-LLR)
(As of 2019-11-10 21:32:24 UTC)
28717 tasks have been sent out. [CPU/GPU/anonymous_platform: 28677 (100%) / 0 (0%) / 40 (0%)]
Of those tasks that have been sent out:
3811 (13%) were aborted. [3811 (13%) / 0 (0%) / 0 (0%)]
1930 (7%) came back with some kind of an error. [1930 (7%) / 0 (0%) / 0 (0%)]
16179 (56%) have returned a successful result. [16140 (56%) / 0 (0%) / 39 (0%)]
6797 (24%) are still in progress. [6796 (24%) / 0 (0%) / 1 (0%)]
Of the tasks that have been returned successfully:
4414 (27%) are pending validation. [4401 (27%) / 0 (0%) / 13 (0%)]
11655 (72%) have been successfully validated. [11629 (72%) / 0 (0%) / 26 (0%)]
60 (0%) were invalid. [60 (0%) / 0 (0%) / 0 (0%)]
50 (0%) are inconclusive. [50 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=21790046. The leading edge was at n=20981446 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.85% as much as it had prior to the challenge!
So, we're nearing about 4 % increase in the leading edge. Since higher n require more work, what would be the work % increase in the project? This would be an interesting statistics to also see for the challenges.
I would guess it could easily be double than the increase in the leading edge? So could we have work-wise advanced the project something like over 10 %?
|
7)
Message boards :
Fermat Divisor Search :
Fermat Divisor Search
(Message 134247)
Posted 1320 days ago by Myrskylyhty
Do you know roughly how long it will take for PPS-Div primes to make the top 100 and get official announcements?
Current digit length for top 100 is 1,689,060. We'll reach that digit length at around n=5,610,936. Current leading edge is at n= 4,944,919.
According to Mike's last two post, the leading edge n went up about 75,000 in 4 days. With that we could reach top 100 in about 36 days, but since there is a FFT length increase incoming and other challenges ongoing, a more careful estimate might be about 50 days or more. Of course it depends on how much people crunch. :)
|
8)
Message boards :
Seventeen or Bust :
The SoB Double Check is DONE!!!
(Message 133618)
Posted 1338 days ago by Myrskylyhty
So, still a chance that the DC yields a prime ;)
|
9)
Message boards :
Fermat Divisor Search :
Fermat Divisor Search
(Message 133397)
Posted 1345 days ago by Myrskylyhty
So, 24 days for 4 %, which translates into 6 days per 1 %.
That's 576 days left, which means we would finish on 28.4.2021.
But I estimate that the challenge + multithread efficiency + new hardware could mean that we finish during next year. Let's see :)
|
10)
Message boards :
Fermat Divisor Search :
Fermat Divisor Search
(Message 133016)
Posted 1356 days ago by Myrskylyhty
I did a bit of checking into FFT size increases:
k=11:
FFT length 288K: n = 4,713,563
FFT length 320K: n = 5,262,883
FFT length 384K: n = 5,865,205
FFT length 400K: n = 7,008,845
FFT length 480K: n = 7,288,505
FFT length 512K: n = 8,694,807
k=49:
FFT length 288K: n = 4,431,064
FFT length 320K: n = 4,945,072
FFT length 384K: n = 5,512,082
FFT length 400K: n = 6,585,098
FFT length 480K: n = 6,847,102
FFT length 512K: n = 8,165,124
FFT length 576K: n = 8,718,132
|
Next 10 posts
|
