332.2M - 333.9M (aka 100M digit range)

[petrw1]

Originally Posted by CADavis

Yeah I switched to Vista 64-bit and it's going approx. twice as fast :-)
Is there a way to make the benchmark go to 74bit factors?

Whoo Hoo I just ordered a new Q9550 with Vista64 ... due Tuesday.

Watch me factor now.

[CADavis]

I think I'm changing my mind a bit. I figured out how to use the Factoring Effort page to make a worktodo file, and I think I want to do a wide range to lower levels.

So what I'm thinking now is to take my current range to 68 bits, then to 70 bits (maybe not though), then start on a new range from 61 - 64 bits

the new range will be starting at 332900021 and eventually go to 332999959, which is all only done to 61 bits.

what do you think, Uncwilly?

[Uncwilly]

Fair enough. I haven't been tracking that area at the moment.


I am currently trying to clear areas ahead of the LL'ers. I have a few cores doing expos (even those assigned, but showing no signs of more TF) up to 73.


It looks like someone found a factor up in the 73 bit range. :)

[jinydu]

I've found the usernames of two 100M digit LL testers:

simcon M332193833 and M332193859
jr007j M332194253 and M332194277

[Uncwilly]

Originally Posted by jinydu

I've found the usernames of two 100M digit LL testers:

simcon M332193833 and M332193859
jr007j M332194253 and M332194277

There are several others that have expos assigned to them. Some are active, some seem not to be.

[Uncwilly]

Here is a progress status report for the range from 332192831 to 332259937

Date					11/20/2008
Average bit depth for first 100 expos	71.46
Average bit depth for first 1000 expos	67.96
100th active expo (no factor found)	332197793
1000th active expo (no factor found)	332239723
Unitless total effort number		813536
Number of first 100 exos to 2^71	45
Number of first 1000 exos to 2^70	275

Bit	# to bit level or higher  
61	1527
62	1259
63	1258
64	1258
65	900
66	849
67	836
68	571
69	280
70	275
71	107
72	84
73	72
74	48
75	10
76	1
77	1

[James Heinrich]

I grabbed M332203901 a couple weeks ago. So far I've completed TF from 2^71-2^75, as I write this P-1_stage1 is 60% done (P-1 both stages should be done around 10-Dec, then I'll (probably) let it continue TF up to 2^77, which will take me into Feb2009(?). I'll unreserve it once it gets to LL time; I don't have the patience to wait until May 2013 to confirm it's not prime

[James Heinrich]

I noticed that M332252939 to M332292827 have currently only been TF'd to 2^61, so I figured it would only take me about 12 hours to bring those 1000 exponents up to 2^63, so probably by the time anyone reads this they'll all be at 2^63. Hopefully I'm not stepping on anyone's toes.

[James Heinrich]

Originally Posted by James Heinrich

I noticed that M332252939 to M332292827 have currently only been TF'd to 2^61

1000 exponents TF'd to 2^63; 37 factors found.

[Uncwilly]

Originally Posted by James Heinrich

I noticed that M332252939 to M332292827 have currently only been TF'd to 2^61, so I figured it would only take me about 12 hours to bring those 1000 exponents up to 2^63, so probably by the time anyone reads this they'll all be at 2^63. Hopefully I'm not stepping on anyone's toes.

You stepped on my toes a bit there. But no problem. I was taking the range to M332259937 up to 65. I saw your message and dropped the range. I put the core on to a different range to higher level.

I generally peek at the exponent status report to see if it has been assigned (and then if it has shown activity, a lot of the L-L'ers have shown no progress on the supporting TF or P-1).

[CADavis]

Originally Posted by CADavis

then start on a new range from 61 - 64 bits

the new range will be starting at 332900021 and eventually go to 332999959,

done, 332.9M - 333M to 64 bits, 116 factors found