+1000@43e6 (total: 3000)

P-1 @ 1e9, nothing

+1000@43e6 (total: 4000)

I'll wait for more curves @43e6 until I load the big gun ;)

+1000@43e6 (total: 5000)

+1000@43e6 (total: 6000)

On the positive side, this number could eventually provide a record ECM factor....

+1000@43e6 (total: 7000)

How many @43e6 should be done?

100 curves complete at 11e7.

[QUOTE=EdH;330875]+1000@43e6 (total: 7000)

How many @43e6 should be done?[/QUOTE]

Ed-
The readme that comes with ECM says 7500 for the default B2. I think now is a good time to move up to 11e7.

What level of ECM is called for in this case? Is the rule of thumb 30%, which would be 52 digits or so? A T55 is just under 18k curves at 11e7- would 52-digits be roughly one-third a T55?
-Curtis

With yoyo@home on the job, a full t55 or even a 2t55 seems reasonable to me (assuming yoyo concurs :smile:)

Yup, with yoyo@home on board, we can easily reach at least t55.

Even if I once had the RSALS clients crunch on a GNFS 172 with 14e (using a poor polynomial, at that) as a stopgap measure during the fantastic power surge which occurred before we shut down, GNFS 172-173 is significantly beyond the 14e/15e efficiency cutoff, so it is probably unreasonable for me to queue this C173 to NFS@Home's 14e...

[QUOTE=debrouxl;330904]Yup, with yoyo@home on board, we can easily reach at least t55.

Even if I once had the RSALS clients crunch on a GNFS 172 with 14e (using a poor polynomial, at that) as a stopgap measure during the fantastic power surge which occurred before we shut down, GNFS 172-173 is significantly beyond the 14e/15e efficiency cutoff, so it is probably unreasonable for me to queue this C173 to NFS@Home's 14e...[/QUOTE]

Even if you could, there's nowhere this sequence will go but up. Based on discussion, I'm relatively certain we're all pretty bored of it. The only reason to factor this number would be to attempt a large(ish) team sieve -- whose purpose would be defeated if NFS@Home ran the job. :smile: