Perhaps the independent LMHs should claim ranges?

[chalsall]

Originally Posted by petrw1

Just noticed you were working in the 176-177M ranges....
I was kindof hoping you would leave the 100M range to those will small PCs.

Only for a few hours... Had to do an emergency server upgrade, so I redirected my proxy domain's A record to CNAME to PrimeNet so my cluster could keep working.

[petrw1]

Originally Posted by chalsall

Only for a few hours... Had to do an emergency server upgrade, so I redirected my proxy domain's A record to CNAME to PrimeNet so my cluster could keep working.

NP....I will take the following as evidence of server maintenance.

The Great Internet Mersenne Prime Search
Visualization Tool

Updated: 1970.01.01 00:00 UTC

[chalsall]

Originally Posted by chalsall

I would like to next reserve 710M to 730M and 650M to 680M.

OK. These ranges will be finished in about 30 hours.

I would like to next reserve 610M to 650M, which will take me about five days to complete.

[chalsall]

Originally Posted by chalsall

I would like to next reserve 610M to 650M, which will take me about five days to complete.

OK. This range is now complete.

Since there's nothing left above 198M at 63 "bits" not claimed and/or reserved by others, my cluster has begun regular LMH-TF and DC work.

It's been fun guys....

[Uncwilly]

Originally Posted by chalsall

Since there's nothing left above 198M at 63 "bits" not claimed and/or reserved by others, my cluster has begun regular LMH-TF and DC work.

Nice.

[petrw1]

Originally Posted by chalsall

OK. This range is now complete.

Since there's nothing left above 198M at 63 "bits" not claimed and/or reserved by others, my cluster has begun regular LMH-TF and DC work.

It's been fun guys....

Another milestone....congrats....and yes it has been fun.

RIP - 32 bit architecture

[chalsall]

Originally Posted by petrw1

RIP - 32 bit architecture

Not that that is necessarily a bad thing, IMHO...

Just so you all know, I've invested a bit of work over the "Crop Over" long weekend here in Bim, and have implemented SNMP on all my clients' machines where I have a Linux machine I can use for SNMP "Gets". ("SpeedFan" and "SpeedFan SNMP Extension" for anyone interested. Bloody M$ don't expose such machine-health data natively.)

Thus, I'm able to bring approximately 150 cores over to DC work, rather than just 75, leaving most of the last of the 63 -> 64 "bit" factoring work to others.

[lycorn]

Originally Posted by chalsall

Thus, I'm able to bring approximately 150 cores over to DC work, rather than just 75

Now that´s good news!

[Uncwilly]

Originally Posted by chalsall

Since there's nothing left above 198M at 63 "bits" not claimed and/or reserved by others, my cluster has begun regular LMH-TF and DC work.

Can I put in a small request?
What do you think about having you cluster working on range from 332,400,000 to 332,999,999? Just marching them up one bit level at a time until what ever level suits you, maybe 70. Then working on the 333,xxx,xxx range.

In he attached, you can see the percentage of exponents that have been factored out. I would love to drive that up for the early parts of the 100M digit range.

[chalsall]

Originally Posted by Uncwilly

Can I put in a small request? What do you think about having you cluster working on range from 332,400,000 to 332,999,999? Just marching them up one bit level at a time until what ever level suits you, maybe 70. Then working on the 333,xxx,xxx range.

OK. I've configured my cluster controller to spend part of its time to begin by bringing 332.7M to 333M up to 67, and 333M to 334M up to 66.

[Uncwilly]

Originally Posted by chalsall

OK. I've configured my cluster controller to spend part of its time to begin by bringing 332.7M to 333M up to 67, and 333M to 334M up to 66.

Cool, I have noticed this.