Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4320BC64.5060003@apache.org>
Date: Thu, 08 Sep 2005 15:34:12 -0700
From: Doug Cutting <cutting@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720)
MIME-Version: 1.0
To: java-dev@lucene.apache.org
Subject: Re: Uneffective writeBytes and readBytes [FIX]
References: <20050906112407.60110b10.lukas.zapletal@qcm.cz>
 <20050906131502.4865f025.lukas.zapletal@qcm.cz> <4320AA85.2090304@apache.org>
 <200509082332.49230.paul.elschot@xs4all.nl>
In-Reply-To: <200509082332.49230.paul.elschot@xs4all.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Paul Elschot wrote:
> I suppose one of these cases are when many terms are used in a query. 
> Would it be easily possible to make the buffer size for a term iterator
> depend on the numbers of documents to be iterated?
> Many terms only occur in a few documents, so this could be a 
> nice win on total buffer size for the many terms case.

This would not be too difficult.

Look in SegmentTermDocs.java.  The buffer may be allocated when the 
parent's stream is first cloned, but clone() won't allocate a buffer if 
the source hasn't had a buffer allocated yet, and nothing should perform 
i/o directly on the parent's freqStream, so in practice a buffer should 
not be allocated until the first read is performed on the clone.

So one could add an BufferedIndexInput.setBufferSize() method and then 
call it in SegmentTermDocs.seek(TermInfo), when the df is known and a 
buffer has not yet been allocated.

Doug

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