Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Message-ID: <035101c470c9$92d6bae0$aa87a8c0@ppeddi>
From: "Praveen Peddi" <ppeddi@contextmedia.com>
To: "lucenelist" <lucene-user@jakarta.apache.org>
Subject: merge factor and minMergeDocs
Date: Fri, 23 Jul 2004 11:27:32 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_034E_01C470A8.0BB6C300"

------=_NextPart_000_034E_01C470A8.0BB6C300
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Is anything changed lucene 1.4 regarding mergefactor?
I recently ported to lucene 1.4 final and my indexing time doesnot =
change with change in the merge factor. Increasing minMergeDocs is =
improving my indexing as expected but changing mergefactor is making no =
difference.

If this is the case, I can always go with the default merge factor of 10 =
so I won't run into too many files open problem. But just vary =
minMergeDocs to tune the indexing perf.

Currently I tested with 25K objects and the indexing time is almost the =
same with mergefactor 10 and mergefactor of 100 (kept minMergeDocs =
=3D100 in both cases). I am confident that my indexing time used to vary =
with change in the merge factor before (with lucene 1.3 RC3 I think).


Praveen
**************************************************************=20
Praveen Peddi
Sr Software Engg, Context Media, Inc.=20
email:ppeddi@contextmedia.com=20
Tel:  401.854.3475=20
Fax:  401.861.3596=20
web: http://www.contextmedia.com=20
**************************************************************=20
Context Media- "The Leader in Enterprise Content Integration"=20

------=_NextPart_000_034E_01C470A8.0BB6C300--