... ... ...
We are probably no where near 5% of the total projects resources spent on sieve. If we have spent 1% of our computational effort thus far on sieve I'd amazed.
... ... ...
We are probably no where near 5% of the total projects resources spent on sieve. If we have spent 1% of our computational effort thus far on sieve I'd amazed.
A bit of a wag LOL...
But I took some offense to axn's post. ( sorry to point a finger directly that's not my intent).
As a reality check: sieving from 25P to 200P will eliminate roughly 1-ln(25P)/ln(200P) = 5.2% candidates only. So as a rule of thumb, no more than 5% of resource should be spent in sieving.
So as a reality check could someone run some numbers for me.
1-ln(50P)/ln(200P) =
1-ln(100P)/ln(200P) =
1-ln(150P)/ln(200P) =
and
1-ln(400T)/ln(1P) =
1-ln(500T)/ln(1P) =
1-ln(400T)/ln(600T) =
Also as to
: Prime Grid
1-ln(400T)/ln(600T) = 0.0119
So if we currently sieved to 400T and were thinking about sieving to 600T we should only devote <3% of our total resources? Just checking... on the logic.
I can see the logic of all the logaritms, but i prefer a faster way to calculate efficiency :
Right now i'm popping out a factor a day or so when sieving, and a full PRP-test takes about a month or more. (running 4core, so should correct for that... let's say a week) That means that sieving is about 7 times as efficient as is, so i'll continue sieving :P
@vjs : just a bit more than 1% of total resources... and probably not worth the effort... But hey, we're not even close yet Once sieving reaches 50T we reevaluate, can always switch, but it'd be much better if the PRP-ers switch to us first