mtsieve

[henryzz]

Originally Posted by pepi37

Can you build sr1sieve with mtsieve? I would like to have MT option. It has that option for Linux , but not for windows

If you want multithreaded sr1sieve on windows try wsl.

[pepi37]

Originally Posted by henryzz

If you want multithreaded sr1sieve on windows try wsl.

I can always run it on Linux :)

But if was so easy to implement MT in LLR and if it is easy like that to implement in sr1sieve... ;)

[rebirther]

Another issue with the latest srsieve2:


from 14.06.

g:\sierp-base913>srsieve2 -n2501 -N10000 -P1e9 -W16 -spl_remain.txt -fB
srsieve2 v1.2.1, a program to find factors of k*b^n+c numbers for fixed b and variable k and n
(p4) Removed 1875 algebraic factors for 324*913^n+1 of the form (2*3^2*913^(n/2)+2*3^1*913^(n/4)+1)
(kp) Sequence has algebraic factorization: 74088*913^n+1 -> (42^3)*913^n+1
(kp) Sequence 74088*913^n+1 has 2500 terms removed due to algebraic factors of the form 42*913^(n/3)+1
(p4) Removed 1875 algebraic factors for 334084*913^n+1 of the form (2*17^2*913^(n/2)+2*17^1*913^(n/4)+1)
Sieving with generic logic
Sieve started: 2 < p < 1e9 with 237646250 terms (2501 < n < 10000, k*913^n+c) (expecting 229697511 factors)
  p=135719, 209.3 p/sec, 207211870 factors found at 3.199M f/sec, 0.0% done. ETC 2020-06-26 12:17

from 16.01.

g:\sierp-base913>srsieve2 -n2501 -N10000 -P1e9 -W16 -spl_remain.txt -fB
srsieve2 v1.2.1, a program to find factors of k*b^n+c numbers for fixed b and variable k and n
(p4) Removed 1875 algebraic factors for 324*913^n+1 of the form (2*3^2*913^(n/2)+2*3^1*913^(n/4)+1)
(kp) Sequence has algebraic factorization: 74088*913^n+1 -> (42^3)*913^n+1
(kp) Sequence 74088*913^n+1 has 2500 terms removed due to algebraic factors of the form 42*913^(n/3)+1
(p4) Removed 1875 algebraic factors for 334084*913^n+1 of the form (2*17^2*913^(n/2)+2*17^1*913^(n/4)+1)
Sieving with generic logic
Sieve started: 2 < p < 1e9 with 237646250 terms (2501 < n < 10000, k*913^n+c) (expecting 229697511 factors)
Sieving with generic logic
Split 31687 base 913 sequences into 31687 base 913^1 sequences.
  p=275794661, 4.765K p/sec, 20401086 factors found at 70.73K f/sec, 27.6% done. ETC 2020-06-21 07:32

The split line was missing and only 2 workers of 16 are running, tried several times with the same result.

[Citrix]

I tried your file.
I have to copy the CL folder to mtsieve for it to compile.
gcwsievecl still crashes.

[rogue]

Originally Posted by Citrix

I tried your file.
I have to copy the CL folder to mtsieve for it to compile.
gcwsievecl still crashes.

Let's continue via PM or e-mail.

[rogue]

Originally Posted by rebirther

The split line was missing and only 2 workers of 16 are running, tried several times with the same result.

Please explain what you mean by "same result".

[Citrix]

Originally Posted by rogue

Let's continue via PM or e-mail.

I downloaded the latest version of mtsieve and compiled it. gcwsievecl.exe does work and did not crash.

The cl code is not working properly. I will play with it and let you know.

The make file for version 1.94 is not properly configured for GPU compiling.

[rebirther]

Originally Posted by rogue

Please explain what you mean by "same result".

same issue

[rogue]

Originally Posted by rebirther

same issue

With the latest from sourceforge (2.0.3), I don't see this behavior. After it "splits" I can see that mutliple threads are running due to CPU utilization in Task Manager.

[rogue]

Originally Posted by Citrix

I downloaded the latest version of mtsieve and compiled it. gcwsievecl.exe does work and did not crash.

The cl code is not working properly. I will play with it and let you know.

The make file for version 1.94 is not properly configured for GPU compiling.

Great to hear. Yes, you should use the current version of the makefile, even with 1.9.4.

Originally I had only one exe, which works for most people even if they didn't or couldn't use the GPU code, but some had issues because at runtime it would look for GPU related libraries even if they were not using GPU workers.

For example, there is now App_cpu.o and App_gpu.o. App.cpp is used to build both, but a compiler switch will build different objects.

[rebirther]

Originally Posted by rogue

With the latest from sourceforge (2.0.3), I don't see this behavior. After it "splits" I can see that mutliple threads are running due to CPU utilization in Task Manager.

base S652 was running on all cores with -W16 but S913 did not (Ryzen 3950X) -->latest 2.0.3