[QUOTE=ltd;345829]Finally all received manual ranges imported.
Next task give the DC server something to do again.[/QUOTE]

Excellent! Could you also update the primegrid reservations when you get a chance. Also I am interested in doing some sieving work on the side, could you build a .dat file for me.Thanks. :bow:

I have already requested the latest results from Primegrid.

The latest valid sieve file was this one:

[url]http://www.psp-project.de/test/sievecomb.zip[/url]

That was the combined sieve with SOB.
To make a PSP only file remove the SOB blocks and change the number in the first line.

Is it possible to create a .dat (PSP only) with only the untested values (once you update the Database with results from primegrid) (if this is too much work, I would not spend too much time on it for now.):bow::max:

[QUOTE=Citrix;345847]Is it possible to create a .dat (PSP only) with only the untested values (if this is too much work, I would not spend too much time on it for now.):bow::max:[/QUOTE]

Hi Citrix,

The speedup from doing this is very, very small. I did a few tests on it back when we were still sieving. And it's a very good thing to do the combined PSP/SoB sieving as our project isn't done if their's isn't. It also makes chances of finding factors better, although at the sieve limit we're at they're quite slim either way. :)

-Kai

[QUOTE=opyrt;345851]Hi Citrix,

The speedup from doing this is very, very small. I did a few tests on it back when we were still sieving. And it's a very good thing to do the combined PSP/SoB sieving as our project isn't done if their's isn't. It also makes chances of finding factors better, although at the sieve limit we're at they're quite slim either way. :)

-Kai[/QUOTE]

I agree with you. I am not doing any large scale sieve etc.
Just need the candidates to test something.

Are all ranges under 14M done? What is remaining... we should finish it as high priority!

[QUOTE=Citrix;346041]Are all ranges under 14M done? What is remaining... we should finish it as high priority![/QUOTE]

Assuming you mean first pass tests, PrimeGrid has n=14489501 as lowest untested value. Other than the PG tests we only have the ones in the "pick a range" thread left under 15M.

Edit: And a few tests in progress on the prpnet server. They are all tests that had timed out:
[URL="http://psp-project.de/prptest/prpnetnew13000000.txt"]prpnetnew13000000.txt[/URL] = 2
[URL="http://psp-project.de/prptest/prpnetnew13300000.txt"]prpnetnew13300000.txt[/URL] = 13
[URL="http://psp-project.de/prptest/prpnetnew13350000.txt"]prpnetnew13350000.txt[/URL] = 19
[URL="http://psp-project.de/prptest/prpnetnew13400000.txt"]prpnetnew13400000.txt[/URL] = 7

-Kai

Kai, Have you tested running ppsieve GPU version on the dat file?

From what I understand the runtime will be proportional to the nmax-nmin range size. So we can just sieve a small n range (eg. the PRP tests that we are currently doing) and save some PRP tests. I think this will be faster than doing PRP tests.

I don't have a GPU myself to do any testing.:sos:
Do you have one?
[url]https://sites.google.com/site/kenscode/prime-programs[/url]

[QUOTE=Citrix;346164]I don't have a GPU myself to do any testing.:sos:
Do you have one?
[URL]https://sites.google.com/site/kenscode/prime-programs[/URL][/QUOTE]

Ungelovende on my team an I did some tests now, and ppsieve is not performing well on this. This is from the ATI version:
[CODE]p=83000000021757953, 362.6K p/sec, 0.06 CPU cores, 0.0% done.
p=83000000042467329, 345.2K p/sec, 0.05 CPU cores, 0.0% done.[/CODE]This is from sr2sieve:
[CODE]p=830001203503861, 10076587 p/sec, 0 factors, 0.0% done[/CODE]So sr2sieve is running in circles around ppsieve. We only tested on one k as ppsieve is meant for ranges of k's, not separate k's.

-Kai

[QUOTE=opyrt;346203]Ungelovende on my team an I did some tests now, and ppsieve is not performing well on this. This is from the ATI version:
[CODE]p=83000000021757953, 362.6K p/sec, 0.06 CPU cores, 0.0% done.
p=83000000042467329, 345.2K p/sec, 0.05 CPU cores, 0.0% done.[/CODE]This is from sr2sieve:
[CODE]p=830001203503861, 10076587 p/sec, 0 factors, 0.0% done[/CODE]So sr2sieve is running in circles around ppsieve. We only tested on one k as ppsieve is meant for ranges of k's, not separate k's.

-Kai[/QUOTE]

It will definitely be slower for the whole 50M. How about the speeds for 100K-1M n.
What is the 0.06 CPU mean?
I think it might be slower for PSP as ppsieve does not take into account the low weight of PSP numbers compared to srsieve. This is something we can fix.

[QUOTE=Citrix;346206]It will definitely be slower for the whole 50M. How about the speeds for 100K-1M n.[/QUOTE]
I didn't test that, as we are at n=15M+ now.

[QUOTE]What is the 0.06 CPU mean?[/QUOTE]I believe it is how much CPU that is used to feed the GPU.