Hi,

sorry I've been busy the last days and will be away the following days too.

Cache size and work age aren't that important for ecoinpool because it can create work so fast that the cache never really gets empty.

Max work age is the time that workunits stay in the cache until they are discarded it mainly has to do how "good" you want to support new transactions coming in. On larger pools, this is never really hit, because work is requested faster than cached workunits are discarded; this could even be true for your small pool.

As for the cache size: It is not printed as an info message how the cache is refilled, you'd have to set the server logger to "debug" to see that. The fact that the number never gets below 19 is because the cache is being refilled to 20 only milliseconds after it was accessed. The value of 20 has been determined by watching the cache on a relatively big pool where the cache got below ~15 in only 2% of all cases (that's mostly on block changes, where the cache has to be drained anyway). Maintaining a cache of 20 workunits should be ok for any server as they just take a couple of cycles to make and only use a few bytes of ram.

The essence of all that I said: It's not really worth changing the default settings for those two values as what you gain from tweaking the numbers is pretty much marginal and will probably never impact work delivery at all. If you're really a perfectionist and want to save ~4kb of RAM and 100ms CPU time, then set the cache size to 10.

p2k