1st in 31

[em99010pepe]

The team woke me up. Soon I'll be putting my cores under 9000 port.

[IronBits]

I've moved some of my cores to Ports 4000 and 5000.
So, if you observed my output for Port 8000 falling, that is why.
All the work I do, no matter what port I run on, counts in the stats scores
Needed to balance out the work each Server is doing.

Go Team Go!

[alpha]

Which port is giving work which takes the longest to crunch? I'd like to keep network usage to a minimum.

[IronBits]

All about the same with the exception of Port 9000, which are very fast work units and not part of the Top-5000 primes.
You can set your WUCacheSize to more than 1.
Edit llr-clientconfig.txt and try
WUCacheSize = 10
I wouldn't go above that if you don't have to.

[alpha]

But it will still report each result as soon as the work unit completes, right?

[IronBits]

Dunno, but, if it only fetches every 10, then you have cut 1/2 the bandwidth right?

[alpha]

Hmm. Looking at a console as the client works, it looks like it sends each result straight after the work unit finishes, and immediately replenishes the cache. So it keeps a constantly full cache, rather than running it dry and then filling it up again.

It's no trouble though, just something I need to bear in mind. Crunch on.