Reserved for MF - Sequence 4788

[mdettweiler]

Originally Posted by schickel

I'll put it in to run some curves @ 43e6, but I don't know how long before my heavy duty worker contacts my server (2 hour contact interval); my light duty worker connects at a 15 minute interval....

Are you sure it needs anything at 43e6? I was thinking that the worker's default of a full t40 would be plenty (considering that it was enough for a c132).

[jrk]

I will start a poly search for this c131.

[jrk]

Shall we make this another team factoring run?

Best poly found so far for c131 (still searching):

# norm 1.184609e-12 alpha -7.685437 e 6.481e-11
skew: 908992.68
c0:  3348252158728305644321314746700224
c1:  30656771114397449709790473636
c2: -16505017784500307019592
c3: -122674727487245953
c4:  30153048686
c5:  32640
Y0: -16592015549072479450790701
Y1:  299465985530831

[mdettweiler]

Originally Posted by jrk

Shall we make this another team factoring run?

Well, considering that our earlier C132 only would have taken about 4-5 days, tops, on a reasonably-modern quad-core, a team sieve on a C131 may well end up oversieving it so humongously that we have a hard time doing the postprocessing. Thus, it would be ideal if an individual is interested in doing all of the sieving on this. However, if nobody's interested in going it alone, then of course a team sieve is still workable (though this time we'd have to be especially careful not to oversieve too much). I can volunteer for the postprocessing again if nobody else is particularly keen on doing it.

[10metreh]

The t40 is still nowhere near completion because someone clicked "Stop" on it to make progress on another number.

[henryzz]

Originally Posted by 10metreh

The t40 is still nowhere near completion because someone clicked "Stop" on it to make progress on another number.

various people were fighting all day with someone

[smh]

Thats the reason i don't run my workers anymore

[hhh]

Originally Posted by smh

Thats the reason i don't run my workers anymore

I understand you so well. A queue is a queue is a queue. Unless some rowdy comes and says "Me first". ( I plead guilty, but only once or twice, after waiting two days for my number). While the thing that new jobs get priority is a good thing at low levels, one should not be able to influence the queue for the B1=250000 and 1000000 level. Definitely deserves fixing. H.

[Andi47]

I did P-1 with B1=1e9, B2=1e14, no factor. I started P+1 with the same B1 and B2 bounds (3 runs)

[Andi47]

Originally Posted by Andi47

I did P-1 with B1=1e9, B2=1e14, no factor. I started P+1 with the same B1 and B2 bounds (3 runs)

P+1 done, no factor found.

[Andi47]

Originally Posted by hhh

A queue is a queue is a queue.

Yes, but....

In the database, any new "very high ECM" factorization is queued first (So it's NOT a queue, as in a normal queue, newly arrived persons or things are queued on the LAST position). So if the DB's "queue" a number will have to wait *forever* if the "queue" keeps growing. This increases the temptation to click the "run now" button - and IMHO this needs to be fixed.

I would suggest to:

either queue any new number to at the *end* of the queue as soon as it has been "prepared for very high ecm" (i.e. p+/-1'ed, IIRC)

or run *only* the 25 digits level (i.e. 200 curves at B1=5e4), and THEN put it at the *end* of the queue.

In this case, for example a composite which is queued in 4th position WILL be ECMed as soon as the first three composites are done, and not at St. Glinglin's day.