Short term goal

[em99010pepe]

Take k=1003 off the server, that's your reserved k, test it yourself.

Anon, you're just like Jasong. You run to many projects in parallel on only a few cores.

Carlos

[em99010pepe]

IB, please take k=1003 off the server. Thank you. We don't run personal work from others. We work on NPLB goal, this means dry port 7000. Going back to bed, when I wake up I want this mess cleaned up!!

[IronBits]

Sorry, I wouldn't know how or where to do that.
If you don't want to work with Port 7000, that's ok, it can be a 'private' one until it goes dry.
I can open another port and server for another drive/push anytime you like.

It's a good experiment so I can get my scripts working correctly with multiple ports.
Not going to hurt anyone to run this one dry.
Those that don't want to assist, fine and understandable.
Those that do help on port 7000, thank you.

[mdettweiler]

Originally Posted by em99010pepe

Take k=1003 off the server, that's your reserved k, test it yourself.

Anon, you're just like Jasong. You run to many projects in parallel on only a few cores.

Carlos

Well, let's see how much I've got going in parallel: currently, I've got k=1003 and k=157 reserved. I was originally planning on doing k=1003 myself as a logical extension of the NPLB range, and as for k=157, Gary had volunteered some machines to help with that, so that one is a special case. Right now, the core that would normally be on k=1003 is taking a break from that and doing LLRnet port 7000 to help clean up the 2nd Drive.

So, as you can see, unlike jasong, I am at least on top of what I have reserved, with clear allocations in mind for what cores I'll be doing the work on.

Originally Posted by em99010pepe

IB, please take k=1003 off the server. Thank you. We don't run personal work from others. We work on NPLB goal, this means dry port 7000. Going back to bed, when I wake up I want this mess cleaned up!!

Carlos, sorry if I offended you in any way. I was thinking of it as more an extension of the NPLB range than a personal k--of course, any primes found would be reported by the user who found them, and we would give users credit for work done in the LLRnet stats.

Since k=1003 is only one k up from the top of the NPLB range, I saw it as a logical extension of NPLB. However, if others feel strongly about it, then, IronBits, feel free to take it off the server, it's not that big a deal to me. (Just please, if you do take it off the server, send me the sieve file--I deleted it from my computer when I sent it to you! Yes, I know, really dumb on my part. ) I can finish it myself, as I was prepared to do originally.

[IronBits]

Not changing anything at this time. Come suck on port 7000 and run the server dry.
If for nothing else than to help keep Carlos from getting a headache and keeping his blood pressure down. ;)
I needed it to test my scripts for multiple ports on same project.
So far, looks like llrnet.ironbits.net keeps the knpairs report looking good.

I created a nplb.ironbits.net to go with the crus.ironbits.net ;)

Seems like there are lots of projects that use llrnet server, and it might make it more easier for folks to choose.
nplb.ironbits.net Port# or crus.ironbits.net Port# :)

I was always taught to respect my elders, but, it keeps getting harder to find one.

[mdettweiler]

Originally Posted by IronBits

Not changing anything at this time. Come suck on port 7000 and run the server dry.
If for nothing else than to help keep Carlos from getting a headache and keeping his blood pressure down. ;)
I needed it to test my scripts for multiple ports on same project.
So far, looks like llrnet.ironbits.net keeps the knpairs report looking good.

I created a nplb.ironbits.net to go with the crus.ironbits.net ;)

Seems like there are lots of projects that use llrnet server, and it might make it more easier for folks to choose.
nplb.ironbits.net Port# or crus.ironbits.net Port# :)

I was always taught to respect my elders, but, it keeps getting harder to find one.

That sounds good. If anyone has an issue with running k=1003, then they can simply stop running the server as soon as it starts handing out k=1003 work. IronBits, maybe you can post here when the server crosses over into k=1003 work, so people can clearly know what they're working on?

You can think of it as the port 7000 server simply turning into a "private" server as soon as it runs out of 2nd Drive work--a private server that anyone's welcome to help out on. (Yeah, I know, a paradox of sorts. )

[em99010pepe]

We are a team and we decide as a team. I don't see Karsten, Beyond, Flatlander, AES, Mini-Geek, ....,Gary's opinion.
I think you offended me by forcing the others to test a number that was reserved by you. Your post proved that you are running too much for the current CPU power you have. You only said the conditions ("any primes found would be reported by the user who found them") after I pointed you to the reason.

IB, I won't answer you but I am right as I was with the number of servers. Time is my friend....

Carlos

[IronBits]

Carlos, my preference is to have Servers/Ports that are consistently kept updated with work, knpairs.txt, and folks coming in to get that work done. :)
7000 will be done soon enough, lessons are learned and point taken.

[mdettweiler]

Originally Posted by em99010pepe

We are a team and we decide as a team. I don't see Karsten, Beyond, Flatlander, AES, Mini-Geek, ....,Gary's opinion.
I think you offended me by forcing the others to test a number that was reserved by you. Your post proved that you are running too much for the current CPU power you have. You only said the conditions ("any primes found would be reported by the user who found them") after I pointed you to the reason.

IB, I won't answer you but I am right as I was with the number of servers. Time is my friend....

Carlos

I'm not "forcing" anyone to test any numbers privately reserved by me--if anyone doesn't want to run the server when it starts handing out k=1003 work, that is completely their choice.

And as for my supposedly running too much to handle: I don't know if you read my last post, but in it I said that I was prepared to finish k=1003 on my own originally.

Originally Posted by IronBits

Carlos, my preference is to have Servers/Ports that are consistently kept updated with work, knpairs.txt, and folks coming in to get that work done. :)
7000 will be done soon enough, lessons are learned and point taken.

Yes, I agree, point has been taken and lessons learned, we won't do this again. We can't do anything about it now that it's already in the server, but we won't do it again. Okay?

Now how about everybody relax, take a deep breath, and settle down.

Anon

[em99010pepe]

Originally Posted by Anonymous

I'm not "forcing" anyone to test any numbers privately reserved by me--if anyone doesn't want to run the server when it starts handing out k=1003 work, that is completely their choice.

Let me say I move my cores to server port 7000 because I only want to test k/n pairs from the Team Drive 2. What happens when the change to k=1003 occurs at the middle of the night?

Originally Posted by Anonymous

We can't do anything about it now that it's already in the server, but we won't do it again. Okay?

No? Stop the server, double click the knpairs file and clear k=1003 pairs from it (windows).

BTW, I am veeeeery relax.

[em99010pepe]

Originally Posted by IronBits

Carlos, my preference is to have Servers/Ports that are consistently kept updated with work, knpairs.txt, and folks coming in to get that work done. :)
7000 will be done soon enough, lessons are learned and point taken.

Yep but not with reserved work from another project, RPS.
Please take those pairs off the server. You guys are mixing two project. I won't say more.