LLRnet servers for NPLB

[gd_barnes]

Originally Posted by em99010pepe

I set jobMaxTime to 7 days for C443 because one of the members has machines that are turned off on weekends. I want to eliminate the rejected pairs from him.

Carlos

How about making it 4 days?

Note to everyone on the job max time: If you get k/n pairs off of the servers, you have to get them tested in a certain amount of time or the server will assume they are 'dormant', will be 'returned' to the server, and handed out to someone else for testing. We usually attempt to vary it to higher levels as the test times get longer. Here is the current time that we have for the various servers:

Ports 400 & 5000: 1 day
Ports 7000 & 7500: 2 days
Port 443: 5 days


Carlos or David, please correct me if I'm incorrect on any of these. IMHO, these are at good lengths now. We don't like to have them too long because then we have to wait longer for the k-range or n-range to be officially completed.

I also had a couple of rejected pairs each of the last 2 days on port 7000 because I didn't have internet access on my laptop while I was gone for 2-1/2 days and I had started some tests on them that did not finish before I left. (Had I known that, I would have left the laptop at home.) The pairs were returned to the server and ended up being handed back out to one of MY quads. lol Later on, when I started my laptop back up, it finished them but they had already been done so they were rejected.


Gary

[em99010pepe]

Gary,

The question here is not to force people to stay always connected and to quickly test the candidates but instead to recognize the work done by them without doing doublechecks.
In this case a lot of borged machines are wasting time with doublechecks. 5 days set as job max time for server C443.


Carlos

[gd_barnes]

Originally Posted by em99010pepe

Gary,

The question here is not to force people to stay always connected and to quickly test the candidates but instead to recognize the work done by them without doing doublechecks.
In this case a lot of borged machines are wasting time with doublechecks. 5 days set as job max time for server C443.


Carlos

Do you feel that the other ports should be longer also?

What is typical for other project's servers?

What are other's opinions on this?

[tnerual]

i think that the minimum time you have to set is 3 days ...

that's to fit with "enterprise computer" set off during the week-end ...

on other project time vary from 5 to 60 days

[gd_barnes]

A heads up:

I sent a file for port 7000 to Ironbits early evening Monday (CDT US) but it hasn't been loaded yet (4:30 AM CDT US). I've pulled my cores off port 7000 and put them on port 7500.

With just the few cores that we currently have on 7000, we should be good for ~20+ hours from now.

I'm alerting everyone so that no one new adds anything substantial to port 7000 until another file is loaded. I'll let everyone know when it has been loaded.


Gary

[gd_barnes]

Originally Posted by tnerual

i think that the minimum time you have to set is 3 days ...

that's to fit with "enterprise computer" set off during the week-end ...

on other project time vary from 5 to 60 days

OK, after the 4th drive is over, I'll have David increase the max job time to 3 days on all of his ports.

I think that >=5 days would be too long. I believe most other projects with such a long limit are testing much higher n-values.


Gary

[em99010pepe]

But for the ones who like to run the standard client getting the k/n pairs out of the llrnet servers, the job max time set to 5 days is a good compromise.

[IronBits]

As requested a long time ago by you guys
Port 7000+7500 - jobMaxTime = 2 * 24 * 3600 -- 2 days
Port 400+5000 - jobMaxTime = 3 * 24 * 3600 -- 3 days
The Servers should not be high maintenance to the administrators of said servers.
Adding knpairs too frequently is a bother...
Constantly changing Server parameters is a bother...
Constantly having to do something to the Servers is a bother...
Why can't you all figure out what you want, stop changing your minds and send me knpairs that will last at least a week, so it's as close to set and forget as it can be?

[gd_barnes]

Originally Posted by IronBits

As requested a long time ago by you guys
Port 7000+7500 - jobMaxTime = 2 * 24 * 3600 -- 2 days
Port 400+5000 - jobMaxTime = 3 * 24 * 3600 -- 3 days
The Servers should not be high maintenance to the administrators of said servers.
Adding knpairs too frequently is a bother...
Constantly changing Server parameters is a bother...
Constantly having to do something to the Servers is a bother...
Why can't you all figure out what you want, stop changing your minds and send me knpairs that will last at least a week, so it's as close to set and forget as it can be?

I'm sorry about the problems. Yes, the 4th drive has been a very high maintenance drive. It was almost impossible to anticipate demand and balance the load between the servers due to large #'s of resources coming and going on the effort. I also have to admit that I didn't realize that you had reached a point of frustration with things.

The main thing that we tried to do is avoid large gaps in testing for extended periods hence the files that were smaller than you would have preferred.

You have now received the last file on this drive. Port 7000 will dry in < 2 days and I will request that everyone move to port 7500 to dry it out in a few days after that.

Thanks for putting up with it. Rest assured that current and future efforts will be like you have experienced on ports 400 and 5000, i.e. low maintenance, with new files sent several days ahead of time. With the exception of the remaining k/n pairs on ports 7000/7500, Job max time will remain at 3 days for the foreseeable future on all ports.


Gary

[gd_barnes]

Port 7000 will be completely dried out by ~6-8P GMT Weds. night.

If you wish to continue on the 4th drive, please plan to shift your resources to port 443 or 7500. For those who prefer lower exponents, please consider our 1st or 3rd drives on ports 400 and 5000. Manual files are also available for those drives.

Once port 7000 is dried, there will likely be ~3 days work left in port 7500 and less than that in port 443 at the current level of resources.


Gary

[gd_barnes]

Port 7000 has now dried out. I'm shifting my machines to ports 7500 and 443 now until dried, which should be ~3-4 days. Then it will be back to 400 and 5000.