Team drive #9 k=1005-2000 n=50K-350K

[IronBits]

I'm ready for the knpairs and we will use port 9000.
Once I get it, I need to do a little bit of testing first, then I'll let you guys know when it's ready to come get some.

[gd_barnes]

Originally Posted by IronBits

I'm ready for the knpairs and we will use port 9000.
Once I get it, I need to do a little bit of testing first, then I'll let you guys know when it's ready to come get some.

OK, I need to leave in a bit. I'll send you a file when I set up the drive page in ~10-12 hours but I'll have people hold off connecting to the new server until you are done with your testing.


Gary

[gd_barnes]

Reserving k=1005-1049 for port 9000. The drive is ready to go!


Gary

[IronBits]

Port 9000 is active...

Please go slowly when adding lots-o-boxen as I won't be here, so can't kick it if there is a problem.

[gd_barnes]

Originally Posted by IronBits

Port 9000 is active...

Please go slowly when adding lots-o-boxen as I won't be here, so can't kick it if there is a problem.

OK, ready to go folks...

I would suggest no more than 4 cores per person and no more than about 15-20 cores total to start with. When I get back in a couple of days, I'll add a core or two to it for a while.

Please post in this thread how many cores you will put on the server as you add them.


Gary

[Flatlander]

3 cores at the moment, 4 (total) later.

[henryzz]

i have just put 2 on

[mdettweiler]

Added one core for a short while to check this out a bit. (In other news: I see that we're at ~168K already on k=1005! Wow! Though I guess that's somewhat to be expected considering how fast I was able to move on just one core back when I did k=1003 from 10K-500K on my own with mostly just one core...)

BTW, I noticed this in the first post of this thread:

No manual files will be posted. All tests will be done on the server.

Eh? I hadn't heard that we were doing this. This is kind of confusing. I mean, I don't see how manual files would cause any problems--in fact, considering as how we're doing this drive by k-range and all, I'd think that manual files would be quite easy to administrate.

Max

[gd_barnes]

Originally Posted by mdettweiler

Added one core for a short while to check this out a bit. (In other news: I see that we're at ~168K already on k=1005! Wow! Though I guess that's somewhat to be expected considering how fast I was able to move on just one core back when I did k=1003 from 10K-500K on my own with mostly just one core...)

BTW, I noticed this in the first post of this thread:

Eh? I hadn't heard that we were doing this. This is kind of confusing. I mean, I don't see how manual files would cause any problems--in fact, considering as how we're doing this drive by k-range and all, I'd think that manual files would be quite easy to administrate.

Max

We're at n=168K on k=1005 because David has 6 very fast cores on it.

Ian suggested that it would be a pain to "allow manual reservations" so I just ran with it. lol See his Jan. 5th post. Technically I'm somewhat indifferent but it would be nice to have a drive without posting files. The testing time loss for the older LLR version is minimal at such low n-ranges.

Can everyone please post their opinions on reserving manual files for this drive?

Gotta go now...back on in ~7 hours for a short bit.


Gary

[mdettweiler]

Originally Posted by gd_barnes

We're at n=168K on k=1005 because David has 6 very fast cores on it.

Ian suggested that it would be a pain to "allow manual reservations" so I just ran with it. lol See his Jan. 5th post. Technically I'm somewhat indifferent but it would be nice to have a drive without posting files. The testing time loss for the older LLR version is minimal at such low n-ranges.

Can everyone please post their opinions on reserving manual files for this drive?

Gotta go now...back on in ~7 hours for a short bit.


Gary

Hmm, I see what you're saying. And I can say that it would be nice not to have to continually worry about uploading new manual files for yet another team drive every time we reload the server.

But, how about this: we allow manual reservations, but not pre-posted; files would instead be available on request--sort of like what we did at the end of the 1st and 3rd Drives. That way, we can have manual reservations, yet essentially without any extra admin hassle than it would normally be to reload a server.

Max

[Mini-Geek]

Originally Posted by gd_barnes

Ian suggested that it would be a pain to "allow manual reservations" so I just ran with it. lol See his Jan. 5th post. Technically I'm somewhat indifferent but it would be nice to have a drive without posting files. The testing time loss for the older LLR version is minimal at such low n-ranges.

Can everyone please post their opinions on reserving manual files for this drive?

I think at the very least, you should allow specific manual reservations, but I don't see a need to post files before they're requested. (i.e. don't bother posting manual files without a reservation, but allow manual reservations and send the file when someone does)
Edit: ninja'd