Patricia Shanahan wrote:
On 7/31/2011 1:43 AM, Peter Firmstone wrote:
...
* TaskManager - improve concurrency and remove the dependency on
Task.runAfter() in River code.
...
I'm playing with implementing a subclass of ThreadPoolExecutor that
modifies the number of threads based on the mean number of tasks over
some recent time period. That way, the number of threads will not be a
long term bottleneck, but threads will not be created and destroyed
for short-lived bursts.
I have an on-going concern, for all performance and concurrency work
in River, that we have neither benchmarks nor access to real
installations to instrument and observe.
I'm having the same issue, I've noticed some Sun T2000's becoming
available on ebay for around $1000, 32GB ram, 8 cores which appear as 32
cpu's in the system.
The only problem might be Oracle's licensing, but this is the cheapest
most relevant hardware I can find at present.
Object based benchmarks should be easy enough to create using
MultitreadedTC (included in test/lib), but this doesn't apply to
integration testing and I suspect the current qa suite might have some
concurrency issues too.
Peter.
