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: <FABBF873F68ED311BB35009027D39072CFF41C@darth_bobo.etapestry.com>
From: Scott Ganyo <scott.ganyo@eTapestry.com>
To: 'Lucene Users List' <lucene-user@jakarta.apache.org>
Subject: RE: CachedSearcher
Date: Tue, 16 Jul 2002 09:40:43 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C22CD6.C3446C60"

------_=_NextPart_001_01C22CD6.C3446C60
Content-Type: text/plain;
	charset="ISO-8859-2"
Content-Transfer-Encoding: quoted-printable

I'd like to see the finalize() methods removed from Lucene entirely.  =
In a
system with heavy load and lots of gc, using finalize() causes =
problems.  To
wit:

1) I was at a talk at JavaOne last year where the gc performance =
experts
from Sun (the engineers actually writing the HotSpot gc) were giving
performance advice.  They specifically stated that finalize() should be
avoided if at all possible because the following steps have to happen =
for
finalized objects:
  a) register the object when created
  b) notice the object when it becomes unreachable
  c) finalize the object
  d) notice the object when it becomes unreachable (again)
  e) reclaim the object

This leads to the following effects in the vm:
  a) allocation is slower
  b) heap is bigger
  c) gc pauses are longer

The Sun engineers recommended that if you really do need an automatic =
clean
up process, that Weak references are *much* more efficient and should =
be
used in preference to finalize().

2) External resources (i.e. file handles) are not released until the =
reader
is closed.  And, as many have found, Lucene eats file handles for =
breakfast,
lunch, and dinner.

Scott

> -----Original Message-----
> From: Hal=E1csy P=E9ter [mailto:halacsy.peter@axelero.com]
> Sent: Tuesday, July 16, 2002 12:43 AM
> To: Lucene Users List
> Subject: RE: CachedSearcher
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Doug Cutting [mailto:cutting@lucene.com]
> > Sent: Tuesday, July 16, 2002 1:00 AM
> > To: Lucene Users List
> > Subject: Re: CachedSearcher
> >=20
> >=20
> > Why is this more complicated than the code in demo/Search.jhtml=20
> > (included below)?  FSDirectory closes files as they're GC'd, so you =

> > don't have to explicitly close the IndexReaders or Searchers.
>=20
> I'll check this code, but I think it could hang up with a lot=20
> of opened IndexReader.
> http://developer.java.sun.com/developer/TechTips/2000/tt0124.html
>=20
> (If a lot of searcher is requested ant a writer is always=20
> modificating the index).=20
>=20
> peter
>=20
> --
> To unsubscribe, e-mail:  =20
> <mailto:lucene-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:=20
> <mailto:lucene-user-help@jakarta.apache.org>
>=20

------_=_NextPart_001_01C22CD6.C3446C60--