4 cores (1 slow, 1 medium, 2 fast) on it now (the slow & medium were already on it, and will probably stay awhile so long as it keeps handing out low-n tests).

Edit: What the heck, I'll put the whole octocore on it as well (so 8 fast, 1 medium, 1 slow, where "fast" is .28ms/iter, medium is .55ms/iter and slow is 21.7ms/iter).

Blist, you made the right choice...thanks.

em, you're welcome. :)

Is a day enough to help out? I'm having a lot of fun here, but I do have another project that the octocore is primarily used for (to help keep Free-DC from passing us in d.net OGR). So long as there is low-n work, I don't have any plans to move either of the other machines (P4 or P1) off of NPLB.

[quote=BlisteringSheep;127188]Edit: What the heck, I'll put the whole octocore on it as well (so 8 fast, 1 medium, 1 slow, where "fast" is .28ms/iter, medium is .55ms/iter and [B]slow is 21.7ms/iter[/B]).[/quote](bold mine)
Wow, am I reading that right? 1 hour 45 minutes per test? That's pretty bad.

I have 4 'medium' cores permanently on port 100 until they're no longer needed.

[QUOTE=Mini-Geek;127196](bold mine)
Wow, am I reading that right? 1 hour 45 minutes per test? That's pretty bad.[/QUOTE]

Yup. 200 MHz of original Pentium-MMX goodness. It sure seemed fast a decade ago. :geek: It's my firewall & nameserver, but doesn't like to be left out of the crunching fun.

:alex:

Well, I just saw something that has me perplexed.
I had the server set to maxConnections = 300.
When Beyond's personal proxy hits me for work, 300 would open up and most would just stay there after he was gone.
I changed it to maxConnections = 50 and restarted the server, now when he comes in, one connection opens up and closes when he's gone.
I wonder if there is a 'math' bug in the Server.exe where by if you enter more than a two digit number in maxConnections = it causes the server to go screwy and eventually lock up?
I suppose I could change that to maxConnections = 99 and still be fine.
They way I thought it would work is that maxConnections = 300 would allow 300 simultaneous connections (300 different folks) to hit me at once.
This doesn't appear to be a correct assumption on my part.
Interesting...

[quote=IronBits;127231]Well, I just saw something that has me perplexed.
I had the server set to maxConnections = 300.
When Beyond's personal proxy hits me for work, 300 would open up and most would just stay there after he was gone.
I changed it to maxConnections = 50 and restarted the server, now when he comes in, one connection opens up and closes when he's gone.
I wonder if there is a 'math' bug in the Server.exe where by if you enter more than a two digit number in maxConnections = it causes the server to go screwy and eventually lock up?
I suppose I could change that to maxConnections = 99 and still be fine.
They way I thought it would work is that maxConnections = 300 would allow 300 simultaneous connections (300 different folks) to hit me at once.
This doesn't appear to be a correct assumption on my part.
Interesting...[/quote]
Hmm, quite odd.

As long as nobody's getting locked out, though, then the server wouldn't have 300 constantly "open" connections with Beyond's server at all times, as I think that would lock everyone else out (theoretically).

Anon

Ya, they just sit there in IDLE_WAIT perpetually.
With 50, most I see is 2 or 3 in IDLE_WAIT, then sometimes they just clear up, then Beyond hits again, it opens one instance of port 500, then it closes as soon as he's gone.
He hits me about every 30 seconds right now and gets the same socket number each time, which is a good thing I believe. :)

[quote=IronBits;127233]Ya, they just sit there in IDLE_WAIT perpetually.
With 50, most I see is 2 or 3 in IDLE_WAIT, then sometimes they just clear up, then Beyond hits again, it opens one instance of port 500, then it closes as soon as he's gone.
He hits me about every 30 seconds right now and gets the same socket number each time, which is a good thing I believe. :)[/quote]
Hmm.

How about you set maxConnections to 99? That way, we can be sure that no more connections than necessary are open, but also that you're in as little danger of hitting the limit as possible.

I did do 99, a lot more IDLE_WAITs in the 4000 range than with 50. I put it at 60 for now to see how it works out.
At 60, client comes in on 500 and it closes as soon as that person leaves.
Also, when you exit the Server, it stops quickly, where as before, it would hang on waiting for something or other to happen, so you had to kill it to make it go away.
Having 60 unique systems hitting one port all at the same time is highly unlikely, but I will keep taking it up a notch to experiment. I didn't try 100 (3 digits) to see what that would do, maybe tomorrow evening.