[quote=henryzz;181847]not another c157:doh!:[/quote]

We've been a bit unlucky with big composites - once we got three team sieves in three lines. Only we've only had one c157 (so far), and it could have been much worse...

If you're wondering why 130396 is still lounging around at 108 digits, it is mainly because of big composites (well, big relative to 108 digits). Some sequences don't get many, even with a slow driver like 2*3. In only about 100 lines since reaching 100 digits, it's had a c105, a c104, a c102, a c101, two c99s (three if ECM doesn't crack the one it's on now), and two c96s. :sad: Even worse, they're really packing it in - I seem to be getting one every 6 or 7 lines right now. :cry: A stark contrast to 10212, which didn't have the fastest of drivers but didn't reach a c>100 until it was at about 115 digits. I hope there's a gap soon (and a driver escape). :smile: Anyone have an idea how unlcuky that is (or have I just not noticed the ones that hit eight c105s before reaching c110 with a driver)?

+400 @11e6 curves.

2000 curves at 43M done.

[quote=bsquared;182064]2000 curves at 43M done.[/quote]

In doing so, you "gatesed" the workers (remember that occasion)...

..but these curves are real, so it doesn't matter. :smile:

[quote=10metreh;182069]In doing so, you "gatesed" the workers (remember that occasion)...

..but these curves are real, so it doesn't matter. :smile:[/quote]

I remember someone reporting false curves under that name, yeah :smile:. But does reporting work affect the workers behavior?

[quote=bsquared;182075]But does reporting work affect the workers behavior?[/quote]
Yes. Once the DB sees that enough work has been reported, it takes the number out of the VHL queue. I don't see any problem with what just happened. 2000 curves at B1=43e6 should eliminate or greatly reduce the need for ~1250 more curves at B1=3e6 (what the DB would have run had it continued).

[quote=Mini-Geek;182078]Yes. Once the DB sees that enough work has been reported, it takes the number out of the VHL queue. I don't see any problem with what just happened. 2000 curves at B1=43e6 should eliminate or greatly reduce the need for ~1250 more curves at B1=3e6 (what the DB would have run had it continued).[/quote]

Huh, didn't know that.... learn something every day! Thanks.

I can make up for those lost DB curves tonight with another couple thousand at 43M.

[quote=bsquared;182082]I can make up for those lost DB curves tonight with another couple thousand at 43M.[/quote]

Me thinks we should start poly searching after those are done.

[QUOTE=10metreh;182085]Me thinks we should start poly searching after those are done.[/QUOTE]

I suggest ~8000 curves at 43M. Poly search can be started even now, but sieving should wait till the full t50 ECM.

My 15 attempts at 110M all failed. Not that this is significant compared to the rest but I thought I would report it anyway.

[quote=axn;182090]Poly search can be started even now,[/quote]
Wouldn't it be more efficient to finish all ECM, then do all poly search, then all sieving, then all filtering, instead of letting them overlap?