Team drive #1: k=400-1001 n=333.2K-600K

[Flatlander]

Originally Posted by em99010pepe

You thought well but I changed my mind...let's see if we can find a prime everyday from now on on drive 1.
So we want to finish this by the end of the year?
Carlos

Edit: Made some calculations and at this pace we won't finish Drive 1 until the end of the year. We need Lennart, Glenn, Brucifer, kar_bon, Beyond, henryzz, jokern_3000, Flatlander...

I'm on server #3 so you can't see how little or much I actually do around here. Well, that was my plan until I read "maintained by em99010pepe". lol

[gd_barnes]

reserving n=547.7K to 550K for port 400

[MyDogBuster]

Taking 550.0 - 550.1

[MyDogBuster]

I'm in the process of moving cores from Base 5 to here. I will put them on port 400 for now, until I can determine what I REALLY want them to do over here.

9 cores total (all 2.4 ghz), but it will take me awhile to empty the queues on some. I have more cores remaining on Base 5 doing manual work. Haven't determined what I will do with them yet either.

If anyone has any suggestions as to where to utilize them, fire away.

Hope this helps. Maybe we can beat yearend for this drive.

[gd_barnes]

Originally Posted by MyDogBuster

I'm in the process of moving cores from Base 5 to here. I will put them on port 400 for now, until I can determine what I REALLY want them to do over here.

9 cores total (all 2.4 ghz), but it will take me awhile to empty the queues on some. I have more cores remaining on Base 5 doing manual work. Haven't determined what I will do with them yet either.

If anyone has any suggestions as to where to utilize them, fire away.

Hope this helps. Maybe we can beat yearend for this drive.

I'd suggest putting them all on this drive. Manual ranges or LLRnet...it doesn't matter.

I'm hoping 2 LLRnet rallies by year end will get us there. At the current pace, we're looking at mid-late Jan. I think. I added an 8th quad to port 400 yesterday for at least a couple of days to boost it a little.

Thanks for asking and for your contribution!


Gary

[MyDogBuster]

I'd suggest putting them all on this drive. Manual ranges or LLRnet...it doesn't matter.

Okay, I'll split them up.

Taking 550.1 - 550.7

[em99010pepe]

I think we are averaging 10 000 candidates per day on llrnet.
Mini-Geek and MyDogBuster, how much per day do you guys do with the manual client?

Carlos

[MyDogBuster]

Mini-Geek and MyDogBuster, how much per day do you guys do with the manual client?

I have 8 cores dedicated to manual stuff and 14 on LLRNET.

[Mini-Geek]

Originally Posted by em99010pepe

I think we are averaging 10 000 candidates per day on llrnet.
Mini-Geek and MyDogBuster, how much per day do you guys do with the manual client?

Carlos

One core will run ~3530 in ~30 days, so one core is about 118 per day, making both cores finish a total of 236 (there's the number you were looking for; the rest is just me having fun with stats ) per day. I run ~42.37 times slower than LLRnet, I run about 2.36% of NPLB's drive 1 work. With ~42 more dual core Athlons I'd match the rest of NPLB's drive 1 work (in reality, knowing Athlons LLR much slower than Intels, I wouldn't do that, but in theory that's about right).

[MooooMoo]

I don't know whether this is even worth posting, but could you manually remove the first few candidates from the n=550.9K file? I had access to a relatively fast machine for a short time, and I used it to take a random shot at the top 5000 prime list. Unfortunately, I won't have access to the machine for quite a while, so I won't be able to complete the range. Anyway, the results are:

459*2^550901-1 is not prime. LLR Res64: 476D81B8AB93B4E6 Time : 400.233 sec.
475*2^550901-1 is not prime. LLR Res64: 0CF593645470C446 Time : 409.060 sec.
487*2^550901-1 is not prime. LLR Res64: CE7B8C7C22E1E74A Time : 407.048 sec.
607*2^550901-1 is not prime. LLR Res64: 987FBCF57CD7E716 Time : 410.726 sec.
627*2^550901-1 is not prime. LLR Res64: 7755B1BC5359A82D Time : 408.789 sec.
649*2^550901-1 is not prime. LLR Res64: 78B2F9D69197D8E4 Time : 409.356 sec.
789*2^550901-1 is not prime. LLR Res64: C5617FE2C5D2A6E6 Time : 408.604 sec.
799*2^550901-1 is not prime. LLR Res64: 483A5C4A77086371 Time : 407.735 sec.
805*2^550901-1 is not prime. LLR Res64: EF6B7030B1EC76BA Time : 412.297 sec.
837*2^550901-1 is not prime. LLR Res64: 89055F28C68B79AB Time : 407.490 sec.
855*2^550901-1 is not prime. LLR Res64: 1FC9A2892D6C0D96 Time : 408.525 sec.
927*2^550901-1 is not prime. LLR Res64: F8D6E1C467078C97 Time : 408.293 sec.
551*2^550902-1 is not prime. LLR Res64: 2E8104B214C5ABCB Time : 417.207 sec.
555*2^550902-1 is not prime. LLR Res64: A9612EE36990BF2B Time : 420.103 sec.
585*2^550902-1 is not prime. LLR Res64: A46D22E34D606B12 Time : 422.803 sec.
705*2^550902-1 is not prime. LLR Res64: 47A848A02CEFE25B Time : 415.925 sec.
815*2^550902-1 is not prime. LLR Res64: 496DB2639B7305C3 Time : 412.998 sec.
887*2^550902-1 is not prime. LLR Res64: EB76B9FE9C148B7D Time : 411.161 sec.
893*2^550902-1 is not prime. LLR Res64: EE5D9B1942FF4621 Time : 410.030 sec.
511*2^550903-1 is not prime. LLR Res64: 8BF7E5C25FAD71A3 Time : 408.932 sec.
553*2^550903-1 is not prime. LLR Res64: 19F3F2F8A8AFEA43 Time : 407.125 sec.
559*2^550903-1 is not prime. LLR Res64: DD199F0D0B977CED Time : 411.822 sec.

[Mini-Geek]

542.0-542.6 is complete. lresults attached. Two primes found, already reported.
Estimate for 547.1-547.3 is 11/24. Estimate for full 547.1-547.7 range is 12/16.