I *hate* sized pools.
Ah, Berin, what strategy algorithm are you guys using for size management?
To be honest, the most brain-dead and simple. I only wanted to get the job done--and would have wanted to deal with better algorithms in the future.
Essentially the pool controller polls the pool size every so often, and increases/decreases a fixed amount. The contract is between the PoolManager and the ManagedPool interface. Any alterations to the PoolManager (which only has one implementation for the time being) will change the way the ManagedPool is managed.
When writing the thread pool for jserv (god, 6 years ago), I had the feeling that the optimal size of the pool was when the average size equaled its standard deviation but never came to prove it statistically... is the pool strategy pluggable in fortress?
Essentially. There is a very rudimentary PoolManager that is set up in the Event package. The algorithm in that implementation is hardcoded, but that won't stop anyone from playing around with it.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin