Nice! :smile:

I'll be leaving town for 10 days tomorrow but I'll attempt to squeeze in an update on base 3 before I go if I get the files within the next 6-7 hours or so.

[QUOTE=KEP;434083]Riesel base 3 is complete to n=25000 ...[/QUOTE]
Wow! Congrats! That was really a Sisyphus work!

[QUOTE=gd_barnes;434132]Nice! :smile:

I'll be leaving town for 10 days tomorrow but I'll attempt to squeeze in an update on base 3 before I go if I get the files within the next 6-7 hours or so.[/QUOTE]

Well that is not going to happen. Unfortunantly GoogleDrive stopped uploading file 2 out of 4 sometime during now and last evening, so I still have to upload 3 files (2.6GB total). Well it is worth the wait for the time when you get back and update the webpages.

[QUOTE=LaurV;434154]Wow! Congrats! That was really a Sisyphus work![/QUOTE]

:smile: I guess so, but at least this time mission was succesfull in opposite to what appears to be true in the case of Sisyphus :smile:

Thanks for the congrats and thanks for leading to something new and interesting :wink:

That was a lot of work! But it is only the first step...

[QUOTE=Puzzle-Peter;434249]That was a lot of work! But it is only the first step...[/QUOTE]

Yes, next step to complete is to go to n=100K.

One advantage for the n=25K-100K range is that optimal sievedepth is only 35G per 2G range (maybe less if you stop and test and remove primed k's).

For future reference, if starting several new 1 or 2G ranges, we have to find a solution that brings us outside of GoogleDrive. Now I'm on my third retry to upload the 2 remaining files on ~926MB (rar compressed) to my google drive. Anyone has a suggestion on where or how we can setup a solution where we could either use FTP or a file of at least 2GB can be uploaded without interruptions?

If we do not find a solution that works better than GoogleDrive and easier than Dropbox, then I'm afraid that I'll not start up any new work. It just is too much of a hazzle to use GoogleDrive, when you have to abort failed uploads and retry 3 times or more :smile:

[QUOTE=KEP;434298]Yes, next step to complete is to go to n=100K.

One advantage for the n=25K-100K range is that optimal sievedepth is only 35G per 2G range (maybe less if you stop and test and remove primed k's).

[/QUOTE]

Sorry, can't help on the Google Drive questions.

What is the optimal sieve depth for a 64G range?

KEP,

Can you share the files through torrent? If so you can send me the files and I'll share/store them on my cloud.

Kind regards,
Carlos

[QUOTE=KEP;434298]For future reference, if starting several new 1 or 2G ranges, we have to find a solution that brings us outside of GoogleDrive...[/QUOTE]

You might try torrents to transfer the data directly to Gary (or whoever else is supposed to receive it or, as Carlos offered, an intermediary).

[QUOTE=masser;434322]Sorry, can't help on the Google Drive questions.

What is the optimal sieve depth for a 64G range?[/QUOTE]

srsieve is barely more efficient for tens of thousands of k's instead of mere thousands. So, the optimal sieve depth hardly changes. For instance, on my sieves from 100k to 500k for R3, working a 2G range means optimal depth about 10% deeper than working a 1G range. If each doubling remains 10% deeper, 64G is 5 doublings of 2G, so optimal depth would be around 60% deeper than it is for 2G. I doubt there's 10% efficiency to gain above ~5G, though, so it could be as low as 15-20% deeper than optimal for 2G.

Of course, there's no reason to sieve the entire 64G range for 25-100k, since quite a bit is already done to 100k. Also, KEP is correct that testing part of a range before finishing the sieve both reduces the time spent sieving and increases the optimal depth; a plan such as sieve to 15G, test 25-35k, remove k's, sieve to 30G, test 35-50k, remove k's, sieve to 45G and test the rest is likely to reduce the total time to complete 25-100k sieving + testing combined vs sieving to 35G and then testing the entire file.

KEP- File transfers for 25-100k work will be orders of magnitude smaller than your 0-25k work. I bet google drive will be fine for working 2G or 4G ranges from 25-100k.

[QUOTE=masser;434322]Sorry, can't help on the Google Drive questions.

What is the optimal sieve depth for a 64G range?[/QUOTE]

I concur with VBCurtis on his answer. You seem to sieve at a slower rate, if you sieve more k's. It is also as VBCurtis declares, that you have a little, however not very high efficiency gain on sieving 64G compared to 2G. Without having digged into the numbers, I'm pretty sure that VBCurtis is close to (if not entirely) correct.