Reserving S653 to n=200k for matzetoni

[QUOTE=matzetoni;509333]Reserving S653 to n=200k for matzetoni[/QUOTE]


Since there isn't a lot of history to go on for you: Can you tell us a little about yourself and your resources? Thanks! :smile:

Thought I just do it like everyone else here.
I'm coming from PG. At some point I got interested in how to use prime finding software, so I learned how to do sieve and testing and quickly started an own prime finding project. Now I want to try something different, like helping out a little at this project.



I have only one machine (not 24/7 crunching, but most of the day), so I don't expect to complete a range within a few days. I will try to make constant progress, but I think the range I took will need a few months (running 1 core). I may split the sieve file to use multiple cores on it and speed things up.



I attached some first results I got, tell me if there is something I could do better.

[QUOTE=matzetoni;509400]Thought I just do it like everyone else here.
I'm coming from PG. At some point I got interested in how to use prime finding software, so I learned how to do sieve and testing and quickly started an own prime finding project. Now I want to try something different, like helping out a little at this project.

I have only one machine (not 24/7 crunching, but most of the day), so I don't expect to complete a range within a few days. I will try to make constant progress, but I think the range I took will need a few months (running 1 core). I may split the sieve file to use multiple cores on it and speed things up.

I attached some first results I got, tell me if there is something I could do better.[/QUOTE]

Results look good.

Just so you know: Tests near n=200K will take 4 times as long as tests at n=100K. If you are running on 1 core less than 24x7, the reservation is likely to take nearly one year. You'll likely want to split it over several cores fairly quickly. Most people use well more than one core on this project.

To get an estimate of how long it will take,I would encourage you to run a test near n=160K. Take the amount of time it takes to test that and multiply by the number of tests in the file. That will be approximately how much CPU time it will take you.

Thanks for your reply, I splitted the file into single k's and now run them separately. Is it OK to report the results by k once they are finished?

Reserving R589 to n=300k (100-300k) for BOINC

[QUOTE=matzetoni;509506]Thanks for your reply, I splitted the file into single k's and now run them separately. Is it OK to report the results by k once they are finished?[/QUOTE]

That is OK.

Reserving S507 to n=300k (100-300k) for BOINC


Reserving S518 to n=300k (100-300k) for BOINC


Reserving R633 to n=300k (100-300k) for BOINC

R712 tested to n=400k (300-400k)

nothing found, 1 remain

Results emailed - Base released

R727 tested to n=400k (250-400k)

nothing found, 1 remain

Results emailed - Base released

Reserving S553 to n=200K for Ian and me.