good call!

Reb,

I don't really understand the need for short deadlines. These prime numbers have been there for an awfully long time and a few days isn't going to make any difference in the long run.

Having said that, you might find fewer WUs timeout if the DCF is corrected. My last batch of long tasks came in with estimates of less than 3 hours yet have taken up to 15 hours to crunch. BOINC wouldn't have downloaded so many had the estimate been more accurate.

Then again, you may be struggling with the same problem as at PG - there isn't a sub-project DCF. Beats me how there wasn't one from the start of BOINC and it's even more incomprehensible that there still isn't.

Okey Dokey, lets find some primes!

S.

Unless you have MANUALLY started a S/R base yourself, you will never really understand why all the work has to be returned back to the server.

After the results are returned (ALL OF THEM), Rebirther has to remove all the K's from the sieve file for each K that was prime.
It's not just one K... for each K there is, for example, 20,000 w/u's for that K depending on the range of N. After that's done, the sieve file (which is the LLR candidate file) is then sieved to a deeper N in preparation for further LLR testing.

God only knows what Rebirther has to do in order to make all of this work with BOINC and to get us a steady stream of work. Which, BTW, has been increasingly more and more steady.


The process is fun, if you're doing it for the first time, and only working on one (1) base....

Rebirther: If I oversimplified the above, my apologies.

Neo
AtP

Well, if we'll never really understand then the rest of your post is redundant. Still, lets have a go, eh?

I didn't say don't return work to the server, I suggested more patience would be appreciated.

The concept is simple. Need to eliminate candidates before taking the next step. Sure, I think we all get that. But the process still doesn't demand a short deadline. What's the big hurry?

Its not as if there is some shortage of other bases or other forms to be crunched, especially now Reb has sorted out multiple bases.

The process just doesn't need short deadlines. This isn't even approaching a systemic need.

You haven't come close to explaining why a short deadline is needed.

You haven't come close to explaining why a short deadline is needed.

You haven't come close to explaining why a short deadline is needed.

plain simple: only after the last wu of a batch has been returned, the results can and have to be evaluated manually.

after that the next batch can be prepared and started.

not that hard to understand - isn't it?

i can do even better...


crunch fast or stay hungry. ;)

Does the server eliminate any remaining tests on the server, for primed k's like SR5 does on PG? If so then just load the ENTIRE sieve file and let the server handle the deletions.
____________

You haven't come close to explaining why a short deadline is needed.

plain simple: only after the last wu of a batch has been returned, the results can and have to be evaluated manually.

after that the next batch can be prepared and started.

not that hard to understand - isn't it?

I also don't understand why reducing the time helps us to get long running tasks back any earlier.
I have a bunch of R648 tasks that seem to be stuck at 99.999% with time remaining 00:00:00 with a running time so far of over 45 minutes.

I am going to agree with Steve Hawker*. We are simply looking for stationary primes not a moving target. The primes will still be there waiting in the same place whether we find them today, tomorrow, or next week. It is not like we are doing code-breaking during war time. I thought that this project is to last for a number of years.

I will not change the deadline for long runners because a prime check needs much more time.

I also don't understand why reducing the time helps us to get long running tasks back any earlier.
I have a bunch of R648 tasks that seem to be stuck at 99.999% with time remaining 00:00:00 with a running time so far of over 45 minutes.

@rebirther:

U seem to be in a hurrry so..

Maybe u should write some information about (minimum requirements) for each app.

:-)

The max success results is 50% working. The task is getting a success but getting no credits. I need to find out whats wrong.