Automated primality testing with LLRnet for CRUS

[IronBits]

Ok, I'll lend a hand for a bit.

[em99010pepe]

Ok, I'll lend a hand for a bit.

Please use port 300 and not 443, faster wu's. Thanks.

[IronBits]

ok,
The server refused your new result :
either someone else computed it already,
either the server is now configured to
work on other numbers.
The server refused your new result :
either someone else computed it already,
either the server is now configured to
work on other numbers.

[em99010pepe]

ok,
The server refused your new result :
either someone else computed it already,
either the server is now configured to
work on other numbers.
The server refused your new result :
either someone else computed it already,
either the server is now configured to
work on other numbers.

That's normal because you changed ports...don't worry, I'll clean the mess from my side.

[IronBits]

Ah, not a problem, just did it once.
How long do you suppose it will take to clear these out?
I assume you have knowledge of my wu completions.
Are there any Stats or we just cleaning up?

[em99010pepe]

Ah, not a problem, just did it once.
How long do you suppose it will take to clear these out?
I assume you have knowledge of my wu completions.
Are there any Stats or we just cleaning up?

Right now the server has 11490 k/n pairs (565 tested as I post) on it but I still need to add something like 122000 pairs. The latter number will be reduced because people are reserving ranges manually. I'm almost finishing my current ranges and I'll jump to this effort not with LLRNet but with the LLR manual client.
This phase, n=320.0k to n=333.2k, can be done in less than a month. Yes, I can see your timings but they don't reflect the real time but the sum of the time necessary to test the number plus the time the client needs to connect to the server. If your wu cache is set to 10 the timings will be 10 times higher.

At this page you can see the progress. Stats are manually, still not automatic, I'll post here in a few days.

We are not just cleaning it up the range, we are filling the gaps for those k's. It's an important task for prime world.

The automatic stats, like the ones you have with PSP PRP and RS5 PRP, are in discussion with Bok and ltd...

Carlos

PS( I'm tired of running a DC project just for the stats but I know it's necessary to bring more people to this effort)

EDIT: I get 90 seconds per candidate on a overclocked quad-core to 2.9GHz. You are getting 250 seconds but they are not the real timings.

[IronBits]

Thanks for the explanations.
140-160 sec is what I'm seeing, but I'm doing more than just this project.
@ 2.5GHz quad core.

[IronBits]

At this page you can see the progress. Stats are manually, still not automatic, I'll post here in a few days.

I'm not seeing my name in lights on that page.
Am I crunching under your name and using your 'proxy' port to crunch work for you automatically so I don't have to reserve anything?