Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of jason.rutherglen@gmail.com
 designates 74.125.92.27 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=CLx9ZhbP0NYIrQfrATGBIT48dPGa5jC8DK1BjVHEZ5R30hHNQ+N3M8BET8oag24mLd
         3auiYUsZB5GT4H1gusaU6MuUNTY0XKrr5IncuNZVLLDH629gpOyZjVPaMScN7oc0DEFn
         s6BpQ1V2pczF1o9a3dkia8CFhvJiz+wezvQA4=
MIME-Version: 1.0
In-Reply-To: <9ac0c6aa0907180912q3114fea4ta752dafaccef57e1@mail.gmail.com>
References: <85d3c3b60907180737te76fa11lffbd0a7f88ae32ae@mail.gmail.com>
	 <9ac0c6aa0907180912q3114fea4ta752dafaccef57e1@mail.gmail.com>
Date: Mon, 20 Jul 2009 16:03:05 -0700
Message-ID: <85d3c3b60907201603y3bc8f39bse522ced325e2ec29@mail.gmail.com>
Subject: Re: Throttling merges
From: Jason Rutherglen <jason.rutherglen@gmail.com>
To: java-dev@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yep, pretty much like "ionice" for Linux.

At the Directory level makes the most sense with the context passed in.

>  then somehow add throttling in there.

Yeah I'm not sure how exactly that will work yet.

On Sat, Jul 18, 2009 at 9:12 AM, Michael
McCandless<lucene@mikemccandless.com> wrote:
> The goal is to be like "ionice" right? =A0Meaning, lower the priority of
> IO caused by merging? =A0I agree that makes sense.
>
> I wonder if we could implement it in the Directory level, so that when
> openInput/createOutput is called we can optionally specify the
> "context" (reader, merging, writer, etc.), and then somehow add
> throttling in there.
>
> Mike
>
> On Sat, Jul 18, 2009 at 10:37 AM, Jason
> Rutherglen<jason.rutherglen@gmail.com> wrote:
>> It may be useful to allow users to throttle merges. A callback
>> that IW passes into SegmentMerger would suffice where individual
>> SM methods make use of the callback. I suppose this could slow
>> down overall merging by adding a potentially useless method
>> call. However if merging typically consumes IO resources for an
>> extended period of time, this offers a way for the user to tune
>> IO consumption and at preferred times free up IO for other
>> tasks.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>

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