Prepare the way! SRBase is coming for the next bit level.

[kriesel]

It would be great if they'd take on some effective P-1 also.

[lycorn]

Never look a gift horse in the mouth...

[Uncwilly]

Originally Posted by lycorn

Never look a gift horse in the mouth...

Originally Posted by Uncwilly

That is not happening though. Gift horses and such.

[tuckerkao]

Originally Posted by Uncwilly

SRBase is turning results in 967M at the 72-73 bit level. Those who are working down in the 120-200 range at the 73 to 74 bit level may want to start up at the 74 bit level now. I know that most folks are watching out, but I figured a heads up would not hurt.

SRBase may have to write the programming codes to skip M168,***,*23 because a lot of them are already at least TF to 75 bits now.

Originally Posted by Uncwilly

That is not happening though. Gift horses and such.

Originally Posted by Uncwilly

I did breadth first somewhat initially up in the 332M range.

I only give the folks who want to run PRPs in the M168M range the breath first.

[slandrum]

Originally Posted by tuckerkao

SRBase may have to write the programming codes to skip M168,***,*23 because a lot of them are already at least TF to 75 bits now.

Why would they do that? They get assignments the way anyone should - they reserve them.

I only give the folks who want to run PRPs in the M168M range the breath first.

You've made it abundantly clear over and over that you are only here for your personal interests and no-one else.

[Uncwilly]

Originally Posted by tuckerkao

SRBase may have to write the programming codes to skip M168,***,*23 because a lot of them are already at least TF to 75 bits now.
I only give the folks who want to run PRPs in the M168M range the breath first.

You like to make everything about you and your randomly chosen pet range. Your range is not even a pimple on the backside of SRBase's work. And if you paid attention you would know that They would not treat that range different than anything else.

[PhilF]

Originally Posted by Uncwilly

They would not treat that range different than anything else.

What would be truly terrible is if a Mersenne prime really is found there, lol!

[Zhangrc]

Originally Posted by kriesel

It would be great if they'd take on some effective P-1 also.

No they won't. TF on GPUs earn MUCH MORE GHZDays than P-1, where the ratio is sometimes 20:1 to 40:1. For those who concern about credit, they won't switch the preferred work type to P-1.

Also, It's MUCH EASIER using mfaktc than CUDAPM1. Just compare the file size! The CUDA runtime DLLs are too huge for some users to download, while mfaktc takes only 1MB. There are many users whose network is too slow to handle the downloading process.

[kriesel]

Originally Posted by Zhangrc

No they won't. TF on GPUs earn MUCH MORE GHZDays than P-1, where the ratio is sometimes 20:1 to 40:1. For those who concern about credit, they won't switch the preferred work type to P-1.

Also, It's MUCH EASIER using mfaktc than CUDAPM1. Just compare the file size! The CUDA runtime DLLs are too huge for some users to download, while mfaktc takes only 1MB. There are many users whose network is too slow to handle the downloading process.

Gpuowl. Works on AMD and most NVIDIA. Small download, better performance. SP/DP ratio varies greatly, therefore TF/(PRP,LL,P-1) does also, versus model.