Author |
Message |
|
Hey all. In preparation for the Winter Solstice Challenge (GFN21) in December, I petition everyone to sieve GFN21 before it! :)
Comparing current sieverate and testing speed on my GTX1070, I calculated that sieving GFN21 is currently 239 times more faster at excluding tasks from the project (counting in the DC) as running the testing. That's a years worth of GFN21 tests in one and a half day.
That said, it would be very desirable to sieve GFN21 as much as possible before the challenge, to increase our chances of finding a record prime worthy of the TOP 6th largest prime ever found! A world-first GFN21 find would also be the largest prime Primegrid has ever found!
I already see heavy hitters like tng* working on it, but we will need the help of everyone to sieve as deep as possible before the challenge :)
(I decided to post this in this subforum, since this is where challenge discussion is mostly had) |
|
|
|
And also it's a very good credit generator! I manually sieved for the first time yesterday and got 12,900 credits for about an hour of crunching. |
|
|
JimB Honorary cruncher Send message
Joined: 4 Aug 11 Posts: 916 ID: 107307 Credit: 974,514,092 RAC: 0
                    
|
Sieving is 1.99 times as efficient as genefer at the moment. While there are a lot more candidates removed than that, they're not candidates we're going to test during the challenge. In fact the 1.99 number is based on the candidates we'll test over the next five years.
The numbers below were as of my last spreadsheet run on June 20, 2018. Next run is in late December.
GFN21 sieving is for b values from 1 to 2G. But our sieve file is for 1 to 100M, since that's the initial sieve we started with. The sieving results graph reflects this - it's as though we're sieving to only 100M. Since we've tested with genefer up to b=247160 (highest b then in progress), any candidate sieved under that value is not useful. The calculated leading edge for five years from now is b=1,005,325. So the current useful range is 1005325-247160=758165. That's 0.00758165 of the 100M sieving range.
We're generating 470/380=1.23684211 sieve removals per 1P sieved. And my benchmarks say that in the time genefer can test one candidate, we can sieve 106.122P. But of course genefer is run twice on every candidate. So we can remove 2*106.122*1.23684211*0.00758165=1.99 relevant candidates in the time it takes to run genefer
As far as affecting the number of candidates we'll actually test during the challenge, sieving is less effective as there's an even smaller range of candidates affected. So while sieving is a good thing, it's certainly not 200x as effective in the short term. |
|
|
|
I also want to help. How can I do this sieving? |
|
|
|
Sieving is 1.99 times as efficient as genefer at the moment. While there are a lot more candidates removed than that, they're not candidates we're going to test during the challenge. In fact the 1.99 number is based on the candidates we'll test over the next five years.
The numbers below were as of my last spreadsheet run on June 20, 2018. Next run is in late December.
GFN21 sieving is for b values from 1 to 2G. But our sieve file is for 1 to 100M, since that's the initial sieve we started with. The sieving results graph reflects this - it's as though we're sieving to only 100M. Since we've tested with genefer up to b=247160 (highest b then in progress), any candidate sieved under that value is not useful. The calculated leading edge for five years from now is b=1,005,325. So the current useful range is 1005325-247160=758165. That's 0.00758165 of the 100M sieving range.
We're generating 470/380=1.23684211 sieve removals per 1P sieved. And my benchmarks say that in the time genefer can test one candidate, we can sieve 106.122P. But of course genefer is run twice on every candidate. So we can remove 2*106.122*1.23684211*0.00758165=1.99 relevant candidates in the time it takes to run genefer
As far as affecting the number of candidates we'll actually test during the challenge, sieving is less effective as there's an even smaller range of candidates affected. So while sieving is a good thing, it's certainly not 200x as effective in the short term.
Yeah I agree :)
I was thinking more in long term in my number, but realistically sieve does not affect the numbers to be tested in the challenge that much. 2x speed is still nice, with the added bonus of more speed long term.
The "calculated leading edge for five years from now" would probably be higher when counting in the sieving also, right? Or is that already calculated in? |
|
|
|
Chara34122 wrote: I also want to help. How can I do this sieving?
I believe you have to do Manual Sieving.
Someone, please, correct me if I'm wrong.
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. |
|
|
|
I also want to help. How can I do this sieving?
"Basically" you go to the Manual Sieving page on http://www.primegrid.com/show_sieving.php, select the "Make Reservation" option, and reserve the length of the interval you want to sieve. Currently my GTX1070 can sieve between 100-200P per day, to give you a sense of scale of the reservations.
In the start you can only reserve small intervals, and the size will go up as you'll return more sieve results.
After you make the reservation, you're taken to an instruction page. Then you can change some options if needed. First, you can select the number of GPU's you'll use (1 for most people).
Then you can play around the B value, which affects the sieving speed, but also the stress on the system. Selecting higher values might give you a speed increase, but you probably cannot use your computer for anything else when sieving. I suggest you stick to B=7 at the start and tinker more later.
If you change any settings, you will need to press "Update" to refresh the Command line switches, which you will need to do the sieve.
For sieving, you'll need to download the executable needed for sieving. For GTX series GPU's, I myself use gfnsvocl_w64_2G.exe. After you download the executable, you will need to start command line or power shell. In windows 10, this is done by right clicking the windows logo, and clicking Windows PowerShell/Command line (Administrator).
After that you will need to know how to use a command line. In this case, you need to navigate to the folder where you downloaded the executable, and then run it using the Command line switch in your instructions page. If you downloaded the executable to your downloaded folder, these two commands are close to what you would need to type in the command line:
cd C:\Users\*your username*\Downloads\
./gfnsvocl_w64_2G.exe *paste command line switches here*
The first one opens the downloads folder, and the second one runs the sieve executable there and starts sieving the range you reserved. If you saved the file somewhere else, change the location accordingly.
After you are done sieving your range, you will need to navigate to your Manual sieve reservations on Primegrid (Manual Sieve -> Show Reservations (any project) -> My Open Reservations), and upload your results there. The name of the file is shown on your instructions page, which you can also access from your reservations page. Make sure you have finished sieving the range before returning it.
As you can see, there are a lot of steps and nyances related to manual sieving, so you need to be aware of what you're doing.
Hope this helps. If someone notices any mistakes in these, please correct me :)
Also see: http://www.primegrid.com/forum_thread.php?id=6395 . Note the disclaimers there ("Manual sieving is not for everyone.", " You can't find a prime with sieving", "
We're not desperate for everyone to start sieving.", "Sieving takes a while.", etc..) |
|
|
JimB Honorary cruncher Send message
Joined: 4 Aug 11 Posts: 916 ID: 107307 Credit: 974,514,092 RAC: 0
                    
|
The "calculated leading edge for five years from now" would probably be higher when counting in the sieving also, right? Or is that already calculated in?
The leading edge for five years from now is calculated in two ways. The larger number produced is the one we use.
The first method is to look at how many genefer candidates we've done since we've started, turn that into a number of candidates per year, then assume we'll do that much plus 10% more work every year over five years. The 10% compounds so by year five the multiplier is 1.61051. The second method is the same but only counts the last six months worth of work. That almost always gives a higher number.
While you could argue that a 10% increase isn't enough, it usually gives enough new sieving to last the six months until I reevaluate the numbers. If we ever ran out of the calculated amount of GFN sieving, I'd reopen them starting from the highest n downwards. GFN 22 and 21 for sure, maybe more. |
|
|
Dave  Send message
Joined: 13 Feb 12 Posts: 2829 ID: 130544 Credit: 954,793,678 RAC: 0
                     
|
Myrskylyhty: very well explained.
[As you can see, there are a lot of steps and nyances related to manual sieving, so you need to be aware of what you're doing.
I thought that said nyancats.
Chara34122: do you have a discreet GPU of recent generation (i.e the last decade)? |
|
|
|
Yes, Radeon RX560 4GB |
|
|
|
For how long PSA points will be pending? |
|
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13513 ID: 53948 Credit: 237,712,514 RAC: 0
                           
|
For how long PSA points will be pending?
It varies from person to person. How fast manual credit gets added depends on your RAC. The higher your RAC, the faster pending PSA credit gets applied. Of course, PSA credit causes your RAC to go up, so it's a self-reinforcing feedback loop. More PSA credit increases RAC, and more RAC increase PSA.
____________
My lucky number is 75898524288+1 |
|
|
|
Less than 240 000 P left now to sieve. I'll try to keep posting statistics every now and then so we can keep up with the speed :) |
|
|
|
Were closing in on 230 000 P left. This implies a rough speed estimate of 5000P per day. If we keep up this speed, we can finish the sieve before the challenge! :) |
|
|
|
Were at about 223 000 P left currently, so it seems to have slowed down a little. The 400P sized ranges can take about 3-5 days to finish so the number goes down in steps.
Avg. speed is at 3400P per day now. Luckily the sieve should speed up as we near the end. |
|
|
|
Were at about 223 000 P left currently, so it seems to have slowed down a little. The 400P sized ranges can take about 3-5 days to finish so the number goes down in steps.
Avg. speed is at 3400P per day now. Luckily the sieve should speed up as we near the end.
If people would try sieving more than one wu at a time it might speed back up again. The User Penguin outlined how to do it, newer higher end gpu's work best for this, but he was running up to 3 wu's at a time on his 1080 gpu. This is NOT for everyone though. |
|
|
|
203830P left! Rate is about 4250P/day.
We can do it! :) |
|
|
Azmodes Volunteer tester
 Send message
Joined: 30 Dec 16 Posts: 184 ID: 479275 Credit: 1,564,594,480 RAC: 0
                      
|
If people would try sieving more than one wu at a time it might speed back up again. The User Penguin outlined how to do it, newer higher end gpu's work best for this, but he was running up to 3 wu's at a time on his 1080 gpu. This is NOT for everyone though.
I got a 1080 Ti and a 1070 Ti in a Ubuntu machine, both msieving. With the OCL app, running more than one instance on a single card is actually slowing things down (270 vs. 230 P/day for the 1080 Ti). That's with B13 and W1.
The CUDA app used to be benefit from multiple instances (6 was the sweetspot for me on my 1060, at least for GFN16), but the OCL app already fully loads the GPUs, so there is no benefit in doing more than one.
Or do you people observe better throughput with multiple instances at lower Bs than with one at maximum B13? Have not played around with that. Honestly, I'm kind of averse to it; I got 10 cards on it right now and babysitting so many instances is messy and annoying. :P
____________
Long live the sievers.
+ Encyclopaedia Metallum: The Metal Archives + |
|
|
|
I'm also getting full and optimal GPU usage on GFN21 sieve by just running one task (GTX1060 and GTX1070). On GFN17 sieve two tasks was optimal.
I think the sieve depth and maybe also the n affects the behaviour. |
|
|
|
Back from my vacation, so I'll be back at it now.
We are at 182700P left now. The total speed has gone down a bit (3000P) per day, but were still advancing nicely. My total speed was something like 370P, so hopefully I can boost it back up a little. |
|
|
Azmodes Volunteer tester
 Send message
Joined: 30 Dec 16 Posts: 184 ID: 479275 Credit: 1,564,594,480 RAC: 0
                      
|
I'll be switching my AMD cards back to MilkyWay soon (with PrimeGrid on the GRC greylist I need to get back some magnitude), but I'll still be able to contribute almost 900 P/day on my green crunchers.
Looks like tng* stopped sieving and is concentrating on Genefer tests now? I don't think we can finish the current range without him before the challenge starts.
____________
Long live the sievers.
+ Encyclopaedia Metallum: The Metal Archives + |
|
|
tng Send message
Joined: 29 Aug 10 Posts: 398 ID: 66603 Credit: 22,925,088,044 RAC: 1
                                    
|
Looks like tng* stopped sieving and is concentrating on Genefer tests now? I don't think we can finish the current range without him before the challenge starts.
Circumstances dictate a hiatus in manual driving -- hopefully I can return soon.
____________
|
|
|
|
167050P left, total speed since my 240000P left post is 3315P/day. With that speed we'd do 132600P before the challenge. So were gonna get close at least :)
Does anyone know if the sieve will speed up anymore when going deeper? |
|
|
dukebgVolunteer tester
 Send message
Joined: 21 Nov 17 Posts: 238 ID: 950482 Credit: 23,670,125 RAC: 0
                 
|
The speed of the sieving will not change |
|
|
|
155161P left! Still at a steady 3500P/day speed.
Seems like we are now at under 19M candidates in the 100M range (in terms of just from sieving)! I guess that means were at over a 81 % sieve "depth". |
|
|
GDBSend message
Joined: 15 Nov 11 Posts: 240 ID: 119185 Credit: 2,577,314,587 RAC: 0
                   
|
155161P left! Still at a steady 3500P/day speed.
Seems like we are now at under 19M candidates in the 100M range (in terms of just from sieving)! I guess that means were at over a 81 % sieve "depth".
No. In the 100M range, there are only 50M candidates (odd numbers only!). 19M remaining out of 50M means 31M factors were sieved out, or 62%. Not 81%. |
|
|
|
155161P left! Still at a steady 3500P/day speed.
Seems like we are now at under 19M candidates in the 100M range (in terms of just from sieving)! I guess that means were at over a 81 % sieve "depth".
No. In the 100M range, there are only 50M candidates (odd numbers only!). 19M remaining out of 50M means 31M factors were sieved out, or 62%. Not 81%.
Yeah that's true if you consider that we "start off" with only the even values of b. Another way to consider would be that the other 50M are sieved away with the number 2, which would lead to the 81 %.
But I guess if the sieve program works only with even b, the 62% depth would actually be more appropriate?
I was gonna include a part about this "62 % or 81 %" in my earlier post, but left that out. Maybe should've left it in.. :P |
|
|
|
We are now at around 100,000P left to reserve. That's 140,000P sieved in 5 weeks, which translates to 28,000P per week or 4000P per day. I think the rate has nicely gone up a little in the past few weeks.
With current rate it could be possible to sieve the whole range before the challenge!
Cheers and thanks everyone! Lets keep at it :) |
|
|
|
As expected, the AP27 challenge put a dent in the sieving speed.
But now, we can still continue sieving for 20 days before the start of the challenge. Lets do our best!
Remember the server migration on Friday, and maybe reserve an extra range or two for manual sieving to not be left without work :) (Remember this also for your CPU projects!) |
|
|
|
We're at 56400P and 13 days left. With the overall rate of 3612P/day, we are currently running a bit short, but lets do our best! Lets do a final push!
Anyhow it goes, we are currently sieved very deep for the challenge! I estimate that during the time of this thread until the challenge, we will have factored about 1% of the current remaining candidates out of the GFN21 project. It is not very large, but it all adds up!
If we were to test all those ~200,000 candidates we will have factored out, it would take 310 years on a GTX1070 and use up about 9 GWh of energy! That's roughly the amount 2,000 large households use up per year! By my estimations, sieving those candidates took about 1/100 of the work and energy than testing them would have! This efficiency however goes down the deeper we sieve. (Disclaimer: these are shaky estimations based on benchmarks on my own GTX1070). |
|
|
SkyFall Volunteer tester Send message
Joined: 26 Mar 15 Posts: 13 ID: 388081 Credit: 56,709,166 RAC: 0
                 
|
I'll be happy to join the sieve :-)
Even tough I'm just a small fish in the pond... |
|
|
|
Only 10920P left! We're now also under 18.9M remaining candidates, meaning that the sieve "depth" is now and extra step deeper; 62,2%/81,1%!
Nice work everyone! Thanks to all sievers, big and small. I think we'll easily finish before the challenge. Just remember to finish all your ranges everyone :) |
|
|
Azmodes Volunteer tester
 Send message
Joined: 30 Dec 16 Posts: 184 ID: 479275 Credit: 1,564,594,480 RAC: 0
                      
|
All ranges have now been reserved, let's see if everyone can finish theirs before the challenge.
____________
Long live the sievers.
+ Encyclopaedia Metallum: The Metal Archives + |
|
|