Quote:
Originally Posted by gd_barnes
That would be a mess!
I would like to do a comparison between srsieve and srsieve2: How many CPU hours did it take you to run that full sieve?
Here is what I did: I sieved P=715M1G in ~8.5 hours on 4 cores. So that's ~34 CPU hours for a P=285M range. Extrapolating: If I sieved the entire range we'd have: 1000M totalrange / 285M range that I sieved * 34 CPU hours = ~120 CPU hours. To be fair, add about ~10% since the higher Pranges sieve faster. Therefore:
I estimate using srsieve it would have taken me ~135 CPU hours to sieve S548 for n=2.5K10K to P=1G.
How does that compare to how much CPU time that it took you running srsieve2?

With W16 around 20h if its working.