Team drive #2: k=400-1001 n=260K-333.2K

[mdettweiler]

316.6-316.8 reserved for IronBits's new LLRnet server test.

[mdettweiler]

279.0-279.4 completed by LLRnet (port 100). lresults attached.

[gd_barnes]

Originally Posted by Anonymous

279.0-279.4 completed by LLRnet (port 100). lresults attached.

Thanks for formatting these and posting them Anon. Could there be a slight bug in your formatting program? I think you may be truncating a potential 1000's digit on the time. For instance, I see some times of 000.0 sec., 043.0 sec., and 085.0 sec., yet at other points I see 88.0 sec., 22.0 sec., and 15.0 sec. I'm thinking that the timings with a zero in the 100's digit should possibly have a 1000's digit.

If it is a bug and is a hassle to fix, since it doesn't affect anything, don't worry about it. It's kind of like those header titles on my web pages.


Gary

[mdettweiler]

Originally Posted by gd_barnes

Thanks for formatting these and posting them Anon. Could there be a slight bug in your formatting program? I think you may be truncating a potential 1000's digit on the time. For instance, I see some times of 000.0 sec., 043.0 sec., and 085.0 sec., yet at other points I see 88.0 sec., 22.0 sec., and 15.0 sec. I'm thinking that the timings with a zero in the 100's digit should possibly have a 1000's digit.

If it is a bug and is a hassle to fix, since it doesn't affect anything, don't worry about it. It's kind of like those header titles on my web pages.


Gary

Actually, I think those odd-looking times were like that before I fed the results files into my processing programs. In that case, it would be a bug in the LLRnet server--as you said, a harmless bug, but a bug nonetheless.

There still is a chance that it could be a bug in one of my scripts--but if it is, then I have no idea what might have caused it. However, I must admit that though I can cobble together some small programs like these ones for processing LLRnet results, I'm still far from being considered even an amateur. (My experience doesn't extend much beyond the scope of my Perl for Dummies book. )

[em99010pepe]

Taking 316.8-320 for IronBits llrnet server.

[em99010pepe]

Just to report that IronBits server is taking from my server the range 310k-315k. Now the two are equilibrated. Cheers to all.

[mdettweiler]

Hi all,

I just changed the various LLRnet reservations listed in this thread (and I'll do the 1st drive thread shortly after) to say which server's reserved that file in addition to denoting that it's reserved by LLRNet. For example, instead of just saying "reserved by LLRnet", it would say "reserved by LLRnet (C100)" if it was reserved by Carlos's port 100 server.

This is partially for my own benefit (so I can easily keep track of which ranges are in what servers, which I need to know when I process the results), but others might find it useful too.

The servers are code-named as follows:
Carlos port 300: C300
Carlos port 100: C100
IronBits port 500: IB
AES port 300: AES

Anon

[em99010pepe]

Please paint green the following ranges on the stats page lol:

268.8-269.0
270.6-270.8
272.4-272.6
274.2-274.4

done

[em99010pepe]

262.6-262.8 done

[em99010pepe]

I'll give to IronBits (I500) the range 305k-310k to equalize both servers.

[em99010pepe]

Please paint green the following completed ranges on the stats page lol:

269.0-269.2
270.8-271.0
272.6-272.8
274.4-274.6