Choose your own K and work on finding a top-5000 prime!

[VBCurtis]

If you run LLR single-threaded at those tiny n-values, you'll get much better production. LLR doesn't multi-thread well when FFT size is smaller than 128K * # of threads.

I'd wait until about n=2 million to bother trying 2 threaded operation.

[storm5510]

Originally Posted by VBCurtis

If you run LLR single-threaded at those tiny n-values, you'll get much better production. LLR doesn't multi-thread well when FFT size is smaller than 128K * # of threads.

I'd wait until about n=2 million to bother trying 2 threaded operation.

Running three threads on each did not work out very well. Doing so produced enough heat to cause the CPU to throttle back when the temperature went beyond 85°C. My older i5 might benefit by reducing it to one thread per instance.

n < 2-million. In theory, I could run four instances on this i7. However, I will keep it at two, single thread each.

Many thanks!

[storm5510]

I am going to lump these here as a group:

k = 98475, Released.
k = 22783, Released.

k = 10019, Active. Testing to >= 1e6.
k = 317605. Active, Testing to >= 1e6.

I will not be posing anything additional in the forums on this subject. Any updates I have will be in kar_bon's Wiki database only. The active k's above were taken from there. No reservations on either. There are enough unreserved there with low n values to last a long time.

[VBCurtis]

Originally Posted by storm5510

I am going to lump these here as a group:

k = 98475, Released.
k = 22783, Released.

How far did you test these?

[storm5510]

Originally Posted by VBCurtis

How far did you test these?

98475 to n = 770,000.
22783 to n = 855,000.

I was frustrated with the progress on a single thread. This was before I started experimenting with multiple instances on multiple machines. I know I did not sieve them deep enough. Probably < 750e9. Everything I sieve now is a single large batch to 15e11. I may go back and pick these up again and take them to n >= 1e6.

[Dylan14]

k = 50171 is at n = 2.055 M, no primes found, continuing. Will likely continue beyond 2.5 M, so if yoyo can sieve up a file for me (up to say, n = 10 M), that would be nice.
k = 17849 - I don't have an update here as the machine running this is over at school and I'm not there due to the virus situation.

[pepi37]

Originally Posted by Dylan14

k = 50171 is at n = 2.055 M, no primes found, continuing. Will likely continue beyond 2.5 M, so if yoyo can sieve up a file for me (up to say, n = 10 M), that would be nice.
k = 17849 - I don't have an update here as the machine running this is over at school and I'm not there due to the virus situation.

50171 will be sent this weekend 😊

[Dylan14]

k = 17849 is at n = 1.524 M, no primes found, continuing...
k = 50171 no change, machine that runs this k is being serviced, so no progress has been made.

[storm5510]

k = 22783 was tested to n = 1e6 ending on 2020-04-28.
k = 98475 is a future project which will also be ran to n = 1e6, or above.

[Dylan14]

k = 17849 reached n = 2M. No primes found. Residues attached - k released.
k = 50171 is at n = 2.286 M, no primes found, continuing...

[Nescro]

Hello, I am new to the concept of manually searching. However, I did manage to search k = 3382599 from the previous n = 50,000 to n = 60,000. This was a test to see if I could take on the task of a bigger search. Now that I completed it. I would like to ask if I could search this value up to around 200k or maybe even higher?