[QUOTE=IronBits;127043]Maybe BlisteringSheep can shift some of his pharmage this way to.
If I can handle Beyond and BlisteringSheep, that would be something. :surprised[/QUOTE]

:tu: I'll throw my octocore :nuke: at if for a little while, see how it shakes. :geek:

:alex:

[quote=em99010pepe;127049]Just keep controlling the size of knpairs.txt, when it gets below 80 Kb it's better to add more work. Tonight I am going to take some numbers from server port 100, because knpairs.txt size is up to 3558 KB size, and post them here to you.[/quote] ok, it is now 373kb.
Thanks for all your help!

[quote=BlisteringSheep;127054]:tu: I'll throw my octocore :nuke: at if for a little while, see how it shakes. :geek:

:alex:[/quote]
I think this is your octo 9830f345
It was getting work just fine, now it appears to connect, then drop. :cry:

sample console output
connection request from 9830f345:63514 (socket 1484)
connection closed (socket 1484)
connection request from 9830f345:63552 (socket 1484)
connection closed (socket 1484)
connection request from 9830f345:63559 (socket 1484)
connection closed (socket 1484)
connection request from 9830f345:63592 (socket 1484)
connection closed (socket 1484)

Beyond is still getting in, but I think he is running a personal proxy server, and it only connects every so often ...
My 8 cores are doing 1 wu and getting more from the Server just fine as well.
Not sure what the problem could be. I even restarted the Server just to make sure I'm ok on this end. /shrugs

[QUOTE=IronBits;127060]I think this is your octo 9830f345
It was getting work just fine, now it appears to connect, then drop. :cry:

sample console output
connection request from 9830f345:63514 (socket 1484)
connection closed (socket 1484)
connection request from 9830f345:63552 (socket 1484)
connection closed (socket 1484)
connection request from 9830f345:63559 (socket 1484)
connection closed (socket 1484)
connection request from 9830f345:63592 (socket 1484)
connection closed (socket 1484)

Beyond is still getting in, but I think he is running a personal proxy server, and it only connects every so often ...
My 8 cores are doing 1 wu and getting more from the Server just fine as well.
Not sure what the problem could be. I even restarted the Server just to make sure I'm ok on this end. /shrugs[/QUOTE]

Yup, that's my IP address. I didn't have any troubles. Only let it run for about an hour on the octo + the Northwood, then put everyone back to their regularly assigned work. I'll check when I get home, but I'm 99.99% positive that all results were sent from both machines w/o error. Actually, the time of your post looks about right, too, for when I finished up. Are you missing any results from me?

IronBits,

More k/n pairs for you. I removed those from my server port 100.

[url]http://celppinho.googlepages.com/NPLB-3100-3150.zip[/url]

Stop the server, add the content at the end of the knpars.txt file.

Carlos

Ok, thanks Carlos. Everything holding steady over here. I think we are ready for another week-end party to clean up. :)

Hi Chaps.
Congrats on your Primes on the 24-hour rally.
Nice to see that no one rolled on a corner or took out a tree :smile:

I succeeded in testing ok prior to the rally on port 300 and 100 but when it came time to go-for-broke the client stalled on port 100 and was not grabbing any work. I saw your posts about the issues so I hopped over to another project to fill in the time.

I am glad to hear that much of these issues have been identified and have either been resolved or are being resolved.

I would like to take the opportunity to request some clarity on the ports now in use (100, 300 and 500). Can you please state the purpose of each port and the planned supply of work to each of these ports? This would help a lot so that planned efforts to assist are clear about which is double-checks, which is primary queue and which is rally &/ testing. If all 3 ports are to be on-fire all the time that would be just fine too. I'd just be more confident about dedicating resource to a LLR port if I knew what the planned work and support level was behind it.

[quote=AMDave;127156]Hi Chaps.
Congrats on your Primes on the 24-hour rally.
Nice to see that no one rolled on a corner or took out a tree :smile:

I succeeded in testing ok prior to the rally on port 300 and 100 but when it came time to go-for-broke the client stalled on port 100 and was not grabbing any work. I saw your posts about the issues so I hopped over to another project to fill in the time.

I am glad to hear that much of these issues have been identified and have either been resolved or are being resolved.

I would like to take the opportunity to request some clarity on the ports now in use (100, 300 and 500). Can you please state the purpose of each port and the planned supply of work to each of these ports? This would help a lot so that planned efforts to assist are clear about which is double-checks, which is primary queue and which is rally &/ testing. If all 3 ports are to be on-fire all the time that would be just fine too. I'd just be more confident about dedicating resource to a LLR port if I knew what the planned work and support level was behind it.[/quote]
All three of those ports are planned to be just as permanent. Port 300 is doing top-5000-range work, whereas port 100 and 500 are not. All of them are first-pass tests. They are all considered just as "primary" and each rally will be different as to which servers are included (though probably port 100 and 500 will go together as they're serving similar ranges of numbers), though we'll probably advise users to put the brunt of their power on port 500 since it should be able to withstand the most traffic.

Hope this helps! :smile:

[quote=AMDave;127156]Hi Chaps.
Congrats on your Primes on the 24-hour rally.
Nice to see that no one rolled on a corner or took out a tree :smile:

I succeeded in testing ok prior to the rally on port 300 and 100 but when it came time to go-for-broke the client stalled on port 100 and was not grabbing any work. I saw your posts about the issues so I hopped over to another project to fill in the time.

I am glad to hear that much of these issues have been identified and have either been resolved or are being resolved.

I would like to take the opportunity to request some clarity on the ports now in use (100, 300 and 500). Can you please state the purpose of each port and the planned supply of work to each of these ports? This would help a lot so that planned efforts to assist are clear about which is double-checks, which is primary queue and which is rally &/ testing. If all 3 ports are to be on-fire all the time that would be just fine too. I'd just be more confident about dedicating resource to a LLR port if I knew what the planned work and support level was behind it.[/quote]

Thanks for your interest Dave. The next rally will be on top-5000 work. But there's another twist here. I'm just about done sieving k=300-400 for n=260K-1M. I'll be done in 2 days. Since I'm not quite done yet, though, files have not yet been posted for it.

I would like the next rally to be for k=300-400 for top-5000 primes. It will be up to the 'server gurus' here [Carlos (em99010pepe), Anon, IronBits, AES] to determine which port to put this range on.

In the mean time, if you'd like to do some testing, as far as we know, ports 100, 300, and 500 are now running very well, the ranges in them are of relatively equal priority, and all have plenty of work in them. But once we post k=300-400 files for manual and LLRnet reservations, they will become higher priority.

Adding more specifics to the ranges for each:
Port 300 is for 400<k<=1001 for n>~350K.
Ports 100 and 500 are for 400<k<=1001 for n<320K.

Anon could give you more particulars about the exact ranges of work for ports 100 and 500 but both are definitely n<320K.


Gary

14 000 candidates need urgently to be tested on [COLOR=Blue][COLOR=Black][COLOR=Green][B]crus.dynip.telepac.pt port 100[COLOR=Black].
[/COLOR][/B][COLOR=Black]Those ones were left behind during last rally due to clients/server issues. Please help. Moved 6 cores to it. I can test them by myself in three days but [/COLOR][/COLOR][/COLOR][/COLOR]:help:needed.
[COLOR=Blue][COLOR=Black][COLOR=Green][COLOR=Black]
Carlos
[/COLOR][/COLOR][/COLOR][/COLOR]

i'm on port 100 too with my quad!