[QUOTE=Andi47;171273]I did P1 with B1=1e9, B2=1e14, no factor. I started P+1 with the same B1 and B2 bounds (3 runs)[/QUOTE]
P+1 done, no factor found. 
[QUOTE=hhh;171262]A queue is a queue is a queue.[/QUOTE]
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 [URL="http://en.wikipedia.org/wiki/Saint_Glinglin"]St. Glinglin's day[/URL]. 
[QUOTE=Andi47;171297]or run *only* the 25 digits level (i.e. 200 curves at B1=5e4), and THEN put it at the *end* of the queue.[/QUOTE]Preferably at the end of the 30 digit level queue after which it moves to the *end* of the 35 digit level queue, etc..

[quote=10metreh;171254]The t40 is still nowhere near completion because someone clicked "Stop" on it to make progress on another number.[/quote]
Sorry about thatI saw that apparently we'd already started a polynomial search on it, and figured that with all the B1=11M work that had been done, we had a full t40 complete which is plenty for this size number. Thus, I hit "stop" to avoid wasting the workers' time. 
[QUOTE=Andi47;171297]or run *only* the 25 digits level (i.e. 200 curves at B1=5e4), and THEN put it at the *end* of the queue.[/QUOTE]
"ECM to high limits" already runs a number to 25digit level (120 curves @ 9e4). So your suggestion is not very helpful (in fact, the whole "preparing" thing is useless once you've run "ECM to high limits"). I'd go with smh's suggestion, with an addition that smaller numbers should be run first before larger numbers. 
[quote=axn;171310]"ECM to high limits" already runs a number to 25digit level (120 curves @ 9e4). So your suggestion is not very helpful (in fact, the whole "preparing" thing is useless once you've run "ECM to high limits").
I'd go with smh's suggestion, with an addition that smaller numbers should be run first before larger numbers.[/quote] people in general dont use "ECM to high limits" because it takes a long time because it uses only one core 
What about inserting the new one at a random position in the queue? Then randomly rotate the queue every few minutes.

840 curves @ 1e6 with b2 9e8 = ~10% of t40
850 curves @ 3e6 with b2 7e9 = ~39% of t40 363 curves @ 11e6 with default b2 = ~53% of t40 we are now at ~102% of t40 
Here is my final poly (used msieve 1.41).
# norm 1.341618e12 alpha 7.037308 e 7.077e11 [code]n: 41044325296244095551421297177058739613282888480930079101779215677896599835732705957943543074751411525745638071656684388489293672281 skew: 501825.58 c0: 197813501589998296714291426614425 c1: 3594640378420732484907428415 c2: 3058781353740944451429 c3: 45948382794399547 c4: 18580727472 c5: 41760 Y0: 15794208298877591694042846 Y1: 271728935426531 rlim: 6000000 alim: 6000000 lpbr: 27 lpba: 27 mfbr: 54 mfba: 54 rlambda: 2.5 alambda: 2.5[/code] Are the parameters I selected OK? [QUOTE=mdettweiler;171249]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.[/QUOTE] Let's do a team sieve, then. 
[QUOTE=henryzz;171331]840 curves @ 1e6 with b2 9e8 = ~10% of t40
850 curves @ 3e6 with b2 7e9 = ~39% of t40 363 curves @ 11e6 with default b2 = ~53% of t40 we are now at ~102% of t40[/QUOTE]You can add 200 curves @ 43e6 (default B2), so it's going to a nice split! 
[quote=schickel;171362]You can add 200 curves @ 43e6 (default B2), so it's going to a nice split![/quote]
that on it's own is ~80% of t40 
Meanwhile, I've started the sieve thread. I'm not a mod here [spoiler](yet)[/spoiler], so please could our worthy moderator put in the new poly and remove the "proposed" from its title?

[QUOTE=schickel;171362]You can add 200 curves @ 43e6 (default B2),[/QUOTE]
Thanks 
Team sieve for line 2382 has completed, producing a C131=P46*P86 factorization:
[code]2382. 864588558624620116627174028234248024151284530600967959183428254564562985214447829513189546277657276453005513317875838138485737430006182150439221712 = 2^4 * 3 * 438849012817399 * 3792916848543091297685310362301268600678979567 * 10821309017625776539139453112614668327856417769647239432607699746391699462546166162743[/code] Next line (C138 cofactor as of this writing) is currently undergoing small ECM at Syd's DB. Guys, how do you think we should proceed for ECM on this one? With the worker queue in such a mess as it is right now, it would be like heck trying to get any work done on a very high limits job. So, unless someone is willing to babysit it and make sure it stays at the top, it might actually be quicker to do it as a distributed job ourselves. (In the meantime, I have put it up for ECM very high limits, but we can stop that run if we decide to do it ourselves.) 
[quote=mdettweiler;172082]Team sieve for line 2382 has completed, producing a C131=P46*P86 factorization:
[code]2382. 864588558624620116627174028234248024151284530600967959183428254564562985214447829513189546277657276453005513317875838138485737430006182150439221712 = 2^4 * 3 * 438849012817399 * 3792916848543091297685310362301268600678979567 * 10821309017625776539139453112614668327856417769647239432607699746391699462546166162743[/code] Next line (C138 cofactor as of this writing) is currently undergoing small ECM at Syd's DB. Guys, how do you think we should proceed for ECM on this one? With the worker queue in such a mess as it is right now, it would be like heck trying to get any work done on a very high limits job. So, unless someone is willing to babysit it and make sure it stays at the top, it might actually be quicker to do it as a distributed job ourselves. (In the meantime, I have put it up for ECM very high limits, but we can stop that run if we decide to do it ourselves.)[/quote] I'll do as much babysitting as possible, but don't expect any of my resources until the downdriver run on 130396 is over. Currently at 90 digits, c86 cofactor. 
[QUOTE=mdettweiler;172082]Next line (C138 cofactor as of this writing) is currently undergoing small ECM at Syd's DB. Guys, how do you think we should proceed for ECM on this one? With the worker queue in such a mess as it is right now, it would be like heck trying to get any work done on a very high limits job. So, unless someone is willing to babysit it and make sure it stays at the top, it might actually be quicker to do it as a distributed job ourselves.
(In the meantime, I have put it up for ECM very high limits, but we can stop that run if we decide to do it ourselves.)[/QUOTE]I'll run some curves on it, in fact I've got it loaded in my server right now, but I'm off to work, so I won't know until after 7PM local what happens. 
I'll run some curves too.

ECM needed: at least t40, incorporating 1000 curves at the 45digit level would be an idea too.
ECM done so far: only 1/3 of t35. [strike]Let's hope my downdriver run ends and I get a driver![/strike] No, I hope it does terminate, but as long as it has the downdriver, I will not be doing any other factorizations or parts of factorizations. 
I am running 750 curves at B1=1e7, using threeeighths of a core i7 machine.

I did 415 curves @ 11e6.

750@1e7 found no factor; proceed to GNFS

Okayline 2383 has completed group GNFS factorization (factors [url=http://www.mersenneforum.org/showpost.php?p=173461&postcount=112]here[/url] and at [url=http://factorization.ath.cx/search.php?id=35442665]Syd's DB[/url]). The next line is stuck at the moment since the TF to 1e7 worker appears to be frozen.

I'm doing some manual work on this with yafu at the moment... getting a few more iterations with easy factorizations.

Are you doing the c107 from line 2386?
[code]13426250388422857716699557092184500820449568993222904193889997607988206118731638115457299967722713612190661[/code] If not, I can run it, unless someone else wants to take it first. 
1000 curves at 1e6 with no factor.

I did 250 with 3e6, no factor

So ECM is complete now. Any volunteers?

If nobody has objection i will do this number with GGNFS.

[QUOTE=Andi_HB;173532]If nobody has objection i will do this number with GGNFS.[/QUOTE]
I just finished it actually: p50*p57= 23231069953404947360434518679383769668374805416437 * 577943694171304833109987600126954777479969654483741073553 
Next line has a c123. I finished 300 curves @ 3e6.

[quote=jrk;173536]I just finished it actually:
p50*p57= 23231069953404947360434518679383769668374805416437 * 577943694171304833109987600126954777479969654483741073553[/quote] Ok i have killed the job. 
[quote=jrk;173537]Next line has a c123. I finished 300 curves @ 3e6.[/quote]
1000 more at 3e6 done. 
[QUOTE=bsquared;173555]1000 more at 3e6 done.[/QUOTE]And with 200@43M & 20@110M, should we call it done and move on to NFS? Anyone want to tackle this alone? If I upgrade the setup on my best system, I could probably do it in three days.....I know there's someone here that could beat me on that.

[QUOTE=schickel;173635]And with 200@43M & 20@110M, should we call it done and move on to NFS? Anyone want to tackle this alone? If I upgrade the setup on my best system, I could probably do it in three days.....I know there's someone here that could beat me on that.[/QUOTE]
123 digits. Should be 48hrs on one core of a Core2 (or 12 hours on 4 cores of a Core 2 Quad). I am _not_ volunteering, BTW :) 
I could probably do it over the weekend if someone provides me a reasonable poly within the next 3 hours.

I'm too late, but I will do a poly search.

Here is a nice poly:
[code]# norm 1.106296e11 alpha 7.271427 e 2.253e10 n: 147998406675517406327680061413386342160268805242427078451900343934549131780622905201645576998223639153399654673028891064447 skew: 485466.48 c0: 51078287402579048322668610790368 c1: 178209989762650404547514616 c2: 1029621170702724248978 c3: 1854024731158621 c4: 5152589890 c5: 3000 Y0: 547802417747206906822973 Y1: 11796075364271 [/code] Best poly I found after searching with msieve on 2 cores for 5 hours. Who wants to take it? 
[QUOTE=jrk;173745]Here is a nice poly:
[code]# norm 1.106296e11 alpha 7.271427 e 2.253e10 n: 147998406675517406327680061413386342160268805242427078451900343934549131780622905201645576998223639153399654673028891064447 skew: 485466.48 c0: 51078287402579048322668610790368 c1: 178209989762650404547514616 c2: 1029621170702724248978 c3: 1854024731158621 c4: 5152589890 c5: 3000 Y0: 547802417747206906822973 Y1: 11796075364271 [/code] Best poly I found after searching with msieve on 2 cores for 5 hours. Who wants to take it?[/QUOTE]I only had an hour or so to do poly selection (with GGNFS) and started sieving with a poly with e ~2e010 I currently have about 8M relations. If someone can do it faster, go ahead, otherwise i'll just et it run. 
[CODE]factoring 147998406675517406327680061413386342160268805242427078451900343934549131780622905201645576998223639153399654673028891064447 (123 digits)
prp61 factor: 9144862946075842082426787599402608124451702752891743405762217 prp62 factor: 16183775257017394245228171463555101602884842615643067477993191[/CODE] The next step is running ECM through the workers 
Nice split

[code]Run 330 out of 1000:
Using B1=3000000, B2=5706890290, polynomial Dickson(6), sigma=1534096427 Step 1 took 8388ms Step 2 took 4139ms ********** Factor found in step 2: 896482203787198998938498849596601211787 Found probable prime factor of 39 digits: 896482203787198998938498849596601211787 Probable prime cofactor 2240984839748758315836634658059607959371667936651269953074814607659897346033187 has 79 digits[/code] 
Line 2390 has a c111. I did 440 curves @ 3e6 and 57 curves @ 11e6.

[QUOTE=jrk;173844][quote=smh][code]factoring 147998406675517406327680061413386342160268805242427078451900343934549131780622905201645576998223639153399654673028891064447 (123 digits)
prp61 factor: 9144862946075842082426787599402608124451702752891743405762217 prp62 factor: 16183775257017394245228171463555101602884842615643067477993191[/code][/quote]Nice split[/QUOTE]Very nice![quote=jrk][code]Run 330 out of 1000: Using B1=3000000, B2=5706890290, polynomial Dickson(6), sigma=1534096427 Step 1 took 8388ms Step 2 took 4139ms ********** Factor found in step 2: 896482203787198998938498849596601211787 Found probable prime factor of 39 digits: 896482203787198998938498849596601211787 Probable prime cofactor 2240984839748758315836634658059607959371667936651269953074814607659897346033187 has 79 digits[/code][/quote]Another very nice split!! 
[QUOTE=jrk;173862]Line 2390 has a c111. I did 440 curves @ 3e6 and 57 curves @ 11e6.[/QUOTE]I'll run a few very high level curves.....does someone else want to tackle the NFS if it comes to that? I just had two jobs finish, so my CPUs are open at the moment.

[QUOTE=schickel;173865]....does someone else want to tackle the NFS if it comes to that? [/QUOTE]I'll take it if no one else has started it already.

[QUOTE=smh;173889]I'll take it if no one else has started it already.[/QUOTE]
Sounds good to me. 
[CODE]164767311827748727812597447590262109111689337122539250119486808338158880846311561568512501683036288516919579549
prp52 factor: 2405628281765591454964486281045414440972614378247653 prp59 factor: 68492423819867585521747025709076292850559624824403044019033[/CODE] Hitting 150 digits. I did a few more steps through the workers. 
I should have the factors of the c107 tomorrow morning.

[QUOTE=smh;173922][CODE]164767311827748727812597447590262109111689337122539250119486808338158880846311561568512501683036288516919579549
prp52 factor: 2405628281765591454964486281045414440972614378247653 prp59 factor: 68492423819867585521747025709076292850559624824403044019033[/CODE] Hitting 150 digits. I did a few more steps through the workers.[/QUOTE]Quick work on that, thanks Sander! Keep your fingers crossed, while the 3 is raised to a higher power we have a better chance of getting rid of it, with the right factorization. The growth rate is going to start hurting pretty quickly, though..... 
The c107 is done (the p35 could have been found with a little more ECM) and in the database.

Currently line 2401, with a c132 which I babysitted in the database queue up to 1/3 of the 40digit level. Will continue tomorrow if it is not finished by then. I think you can start searching for a poly. H.

I did babysit it a little this afternoon. I've been running 60 curves with B1=11M, no luck.
It's time to start thinking about a new team sieve. 
Afraid not:
[code]Using B1=3000000, B2=5706890290, polynomial Dickson(6), sigma=2179057210 Step 1 took 8271ms Step 2 took 4516ms ********** Factor found in step 2: 1056673482676022312579825080018199556649081 Found probable prime factor of 43 digits: 1056673482676022312579825080018199556649081 Probable prime cofactor 249267850007313489951416374237531782339203024789129680307405969334427179825905197320964231 has 90 digits [/code] 
I am NFSing the c99 it is on now.

The guide has changed to 2^6*3^2.

p43 with B1=3M  nice!

[quote=Andi47;174046]p43 with B1=3M  nice![/quote]
The record for B1=3M is 57 (!) digits. 
[QUOTE=jrk;174044]I am NFSing the c99 it is on now.[/QUOTE]
done: [code]prp44 factor: 71178412059395956154457282033398928763835573 prp55 factor: 5063402932122215229228135154799447238044383504436033219 [/code] 
I see a C88! (Not taking it, though.)

[QUOTE=10metreh;174065]I see a C88! (Not taking it, though.)[/QUOTE]
I'm taking it 
Now I am NFSing the c96.
edit: prp36 factor: 891025287830063388764121528298794757 prp60 factor: 119281815318222294187415636388777691053771759897891460941727 
It's starting to get ugly!
Keep your fingers crossed! At an aweinspiring height, we're looking at c154 = 2[sup]7[/sup] * 3[sup]2[/sup] with a c[sub]140[/sub] GNFS job possibly in the future. And it's still in high gear! (In fact with the exponent creeping up one, it's added a little bit of speed.)
We need to catch a lucky break soon! 
[QUOTE=schickel;174080]At an aweinspiring height, we're looking at c154 = 2[sup]7[/sup] * 3[sup]2[/sup][/QUOTE]
Actually, it is 2^7*3^2*17. The good news is that, because of the 17, the 3^2 will stick around. So, with a favourable split, you can drop the 2^7. Bad news is, it ain't gonna be on this iteration. 
ECM efforts are currently around t40; we need to do a few 11e6 curves, maybe 1/3 of t45, before doing a GNFS.

I did 2000 curves @ 3e6.

[quote=jrk;174126]I did 2000 curves @ 3e6.[/quote]
So now well past t40. Team sieve? 
[quote=10metreh;174127]So now well past t40. Team sieve?[/quote]
Sure. I'll be glad to do the postprocessing (plus FTP hostingsame as before, this time in directory c140relations) again if nobody else is particular itching to do it. Any volunteers for a polynomial search? 
msieve wants 58 hours for a poly search, so we may want to split it into parts.

I've started the team sieve thread, so we can do our poly search discussion/coordinating in there now.

[QUOTE=jrk;174126]I did 2000 curves @ 3e6.[/QUOTE]And you can add another 40+ curves @ 43M (default B2).....

1 Attachment(s)
Meanwhile, the side sequence 314718 is at index 8867 !

[QUOTE=schickel;174135]And you can add another 40+ curves @ 43M (default B2).....[/QUOTE]
78@43M, no factor. 
So, we have a new line, but the 2^7 * 3^2 * 17 is still there. There is a C137 as well...

I did 2000 curves @ B1=3e6, B2=default on the c137. No factor.

I did 98 ECM curves at B1=43e6 overnight (B2 = default), no factor.

[QUOTE=jrk;175032]I did 2000 curves @ B1=3e6, B2=default on the c137. No factor.[/QUOTE]
[QUOTE=Andi47;175040]I did 98 ECM curves at B1=43e6 overnight (B2 = default), no factor.[/QUOTE] Can you report your results [URL="http://factorization.ath.cx/search.php?id=38898191&eff=true&detail=1"]here[/URL]? 
My analysis shows that, assuming a 2way split, we have a 5050 chance of losing the 2^7 in this iteration!
[Currently, there are enough factors to assure 2^4. There is a 5050 chance of getting > 2^3 from the remaining factors (from the c137) which will guarantee that 2^7 will persist.] EDIT: A 3way split will however guarantee that 2^7 persists :( 
[quote=axn;175043]Can you report your results [URL="http://factorization.ath.cx/search.php?id=38898191&eff=true&detail=1"]here[/URL]?[/quote]
Added. 
[QUOTE=jrk;175740]We have factors:
[code]prp57 factor: 103318579854944335676030551532196180829653425427361692593 prp81 factor: 323215987055017029160465127314519153559591439982466579069406240925493873545842479[/code] Log attached.[/QUOTE] Next line has a c143. 
[QUOTE=jrk;175742]Next line has a c143.[/QUOTE]
I just see in the database: 7771 curves at 43e6 by Alex Kruppa within only a few hours??? This must be a HUGE cluster..... 
Got an ECM factor of the c143.
[code]Using B1=3000000, B2=5706890290, polynomial Dickson(6), sigma=1112855099 Step 1 took 9656ms Step 2 took 4870ms ********** Factor found in step 2: 531088977736851265980175972579817623709 Found probable prime factor of 39 digits: 531088977736851265980175972579817623709 Composite cofactor 183015474594334048980664757999030271952712067435178305507209636383593062935862719457319693469129406018351 has 105 digits [/code] I am GGNFS'ing the c105 
[quote=Andi47;175752]I just see in the database: 7771 curves at 43e6 by Alex Kruppa within only a few hours??? This must be a HUGE cluster.....[/quote]
The P39 must have been a MASSIVE miss if that was true! 
[QUOTE=jrk;175757]I am GGNFS'ing the c105[/QUOTE]
[code]prp45 factor: 235657500907163308436573633500513257290545453 prp60 factor: 776616377114312792640247126817458598582668273075707980341067 [/code] Next line has a c134. 
[url]http://factorization.ath.cx/search.php?id=39376136[/url] (the c134 at 4788.2410)
[code]850000000 85000000000 193436 Bill Gates June 3, 2009, 11:19 pm[/code]Something tells me that's not entirely accurate... 
Can Syd tell us the IP address that was used to post these bogus results? Maybe we can match it against IP addresses used for posting here.
Alex 
I did 2000 curves @ B1=3000000, B2=5706890290 on the c134.

I am running some 11e6 curves on it. Meanwhile, if someone can get me a reasonable poly within the next 24 hrs, I can finish the whole thing by myself by next Wednesday.

[QUOTE=axn;175837]I am running some 11e6 curves on it. Meanwhile, if someone can get me a reasonable poly within the next 24 hrs, I can finish the whole thing by myself by next Wednesday.[/QUOTE][code]name: a4788
n: 32299880300827036383291069260216240546437982947532075193586864704343482306012701350943737668991851271506016829148932349430377649964591 skew: 566511.72 # norm 4.54e+018 c5: 62160 c4: 84970653748 c3: 50400906361463526 c2: 22608498037500947529427 c1: 8254349633026004383984255604 c0: 764487387105372569952027598371325 # alpha 6.35 Y1: 1009413309108919 Y0: 55352318459081197491472094 # Murphy_E 4.44e011 # M 5451045075518794245451319373483057172745436076954176258939655826956455779115055128915903697457313310053919157605347637622239870551623 type: gnfs[/code]According to defpar.txt, 3.48e11 is a good score. Let me know if this is reasonable enough. 
[QUOTE=schickel;175839]Let me know if this is reasonable enough.[/QUOTE]
More than! With the following parameters (and expected 20M relations), my timing indicates that I can knock this bad boy off in around 60hrs (WCT). Unfortunately, since I am out Saturday thru Tuesday, it doesn't really matter  Wednesday is when you'll get it. So till tomorrow, I'll continue the ecm, and start off the sieving in another 24 hrs. [CODE]rlim: 12000000 alim: 12000000 lpbr: 28 lpba: 28 mfbr: 54 mfba: 54 rlambda: 2.5 alambda: 2.5 qintsize: 100000 [/CODE] EDIT: If somebody with exceptionally strong PERLfu can tell me how to modify factMsieve.pl so that I can report the factor automatically to Syd's database by calling a URL, much appreciate it. EDIT2: If it helps: The url to call is http://factorization.ath.cx/search.php?query=<N>&reportfac=<f>. sub getPrimes in factMsieve.pl is where it scans for factors. 
[QUOTE=axn;175843]More than! With the following parameters (and expected 20M relations), my timing indicates that I can knock this bad boy off in around 60hrs (WCT). Unfortunately, since I am out Saturday thru Tuesday, it doesn't really matter  Wednesday is when you'll get it. So till tomorrow, I'll continue the ecm, and start off the sieving in another 24 hrs.[/QUOTE]Let me know what your cutoff time for the poly is; I can leave the search running until then, just in case something better turns up.

[quote=akruppa;175793]Can Syd tell us the IP address that was used to post these bogus results? Maybe we can match it against IP addresses used for posting here.
Alex[/quote] I think it's one of those babysitters going to the extreme. Maybe a login system where users could be banned would work? For instance, I can submit curves as "Engelbert Humperdinck" or any other jumble of letters in the world. A login system would: 1. Force users to use their own username for curve reporting 2. Allow Syd to ban users who register as "Bill Gates" and the like before they report any curves. 
[QUOTE=schickel;175844]Let me know what your cutoff time for the poly is; I can leave the search running until then, just in case something better turns up.[/QUOTE]
No need. Like I said, this one is good enuf. Unless you can find something now that I can finish in half the time (or if some one gives me the perl code requested 2 posts above) 
[QUOTE=schickel;175844]Let me know what your cutoff time for the poly is; I can leave the search running until then, just in case something better turns up.[/QUOTE]Speak of the devil.....:grin:[code]name: a4788
n: 32299880300827036383291069260216240546437982947532075193586864704343482306012701350943737668991851271506016829148932349430377649964591 skew: 196692.36 # norm 3.21e+018 c5: 149820 c4: 199121342468 c3: 2431270053017823 c2: 534023622995170240720 c1: 402347243349420943307170446 c0: 8217995578349023526551482669520 # alpha 6.20 Y1: 314176237497269 Y0: 46422337570064854626476679 # Murphy_E 4.62e011 # M 6276210936935585364838354084512714308923106809753288115864723557319586271020393200601490969828210413421927466742980111894654459668942 type: gnfs[/code] 
[QUOTE=10metreh;175845]I think it's one of those babysitters going to the extreme. [/QUOTE]
But why pick on this sequence? This is the second time for 4788! Has any other numbers in the VHL queue got shafted like this?? 
[QUOTE=schickel;175848]Speak of the devil.....:grin:[/QUOTE]
Hehe. Well, ok. If you're a glutton for punishment! Keep going for another 24hr or until you tire (whichever comes first). 
It's very odd to pick on 4788. Maybe it's chance and someone's just being naughty?

[QUOTE=axn;175843]More than! With the following parameters (and expected 20M relations), my timing indicates that I can knock this bad boy off in around 60hrs (WCT). [/QUOTE]With what kind of hardware? I've got a dual core I could throw into the mix......[QUOTE]Unfortunately, since I am out Saturday thru Tuesday, it doesn't really matter  Wednesday is when you'll get it. [/QUOTE]Maybe we would gang up on this and do it before Saturday......
I can set up an FTP server on my end and you could upload your relations before you leave...... 
All times are UTC. The time now is 18:01. 
Powered by vBulletin® Version 3.8.11
Copyright ©2000  2022, Jelsoft Enterprises Ltd.