Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (nike.apache.org: domain of pats@acm.org designates
 209.86.89.65 as permitted sender)
Message-ID: <4E35E3F8.7030704@acm.org>
Date: Sun, 31 Jul 2011 16:23:36 -0700
From: Patricia Shanahan <pats@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64;
 rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: dev@river.apache.org
Subject: Re: Future plans
References: <4E351598.409@zeus.net.au>
In-Reply-To: <4E351598.409@zeus.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.

Patricia