Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of simone.tripodi@gmail.com
 designates 74.125.82.49 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=b64pbKzWJk6m34WVnpxROvDClTwjETBErkgwS+kT4AAJO6MHuIFT4eSiUT383XtfBy
         rJWXrUMlJAFOyunszq0gBwJTKvbrKxHrkhdK0R3uUHUpGE99UVvVPLv5bPevzISkDSY7
         vORrlpEMD/utV8jsNbnKHp3cCkjrMdtS09TNk=
MIME-Version: 1.0
In-Reply-To: <AF05E917-B510-4176-AD51-AAE821A776BE@gmail.com>
References: <AANLkTinasLMRBXxrZOh7-gCjvnOUvVbN7VMcCFAhQXiC@mail.gmail.com>
	<AF05E917-B510-4176-AD51-AAE821A776BE@gmail.com>
Date: Thu, 4 Nov 2010 21:31:19 +0100
Message-ID: <AANLkTinEx73N_x7EwFTxSo1JYuXZ2RSeFVN9CXt=XivX@mail.gmail.com>
Subject: Re: [pool] "Smart" (aka auto-configure) pools
From: Simone Tripodi <simone.tripodi@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Steven,
this feature sounds *cool*!!! +1 for me, definitively!
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/


On Thu, Nov 4, 2010 at 8:18 PM, Steve <smsiebe@gmail.com> wrote:
>
> Not Paul, Phil. My bad!
>
> S
>
> On Nov 4, 2010, at 2:34 PM, Steven Siebert <smsiebe@gmail.com> wrote:
>
>> First, Paul, nice presentation at ApacheCon =3D)
>>
>> I came up after the discussion to mention a feature I added to my pool
>> implementation, wanted to record this here and get community thoughts.
>>
>> What I have done for a customer (non-releasable, but I can re-implement
>> much cleaner) was essentially enable the pool to "track" its maintenance
>> operations over a 24-hour period (starting at 0000) to better "predict"
>> configuration changes that needed to take place. =C2=A0This was helpful =
in our
>> dev-to-production deployments for configuration "burn-in"...we could hav=
e
>> guessed what the config for the pool should be...but this helped get it
>> right quickly. =C2=A0We kept it running (intentionally) and detected tre=
nds over
>> the first week. =C2=A0We then turned this feature off (via JMX) and pool=
 could
>> then adjust itself based on it's learned data. =C2=A0Admittedly, this wa=
s a
>> "crude" implementation that was used to improve performance due to our
>> predictable spikes....there is a lot more that could be done.
>>
>> First question: =C2=A0is this coming the community would like?
>>
>> Second: =C2=A0If it is desired, I implemented this by re-implementing th=
e
>> evictor...Paul suggested this might also be a good fit for an "outside"
>> implementation (I can see this, as well)
>>
>> Finally: =C2=A0What features would you like to see?
>>
>> Thoughts?
>>
>> Steve
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org