lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hui" <...@triplehop.com>
Subject RE: Sys properties Was: java.io.tmpdir as lock dir .... once again
Date Thu, 04 Mar 2004 14:42:10 GMT
Not yet. For the compound file format, when the files get bigger, if I add
few new files frequently, the bigger files has to be updated. Will that
affect lot on the search and produce heavier disk I/O compared with the
traditional index format? It seems OS cache makes quite difference when the
files not changed differently.

Regards,
Hui

-----Original Message-----
From: Erik Hatcher [mailto:erik@ehatchersolutions.com] 
Sent: Wednesday, March 03, 2004 9:21 PM
To: Lucene Users List
Subject: Re: Sys properties Was: java.io.tmpdir as lock dir .... once again


On Mar 3, 2004, at 4:25 PM, hui wrote:
> Anoterh similar issue. If we could have a parameter to control the max
> number of the files within the index, that is going to avoid the 
> problem of
> running of the file handler issue.
> When the file number within one index reaches the limit, optimization 
> is
> going to be called.
> Right now, if the file number within one index out of the limit of your
> window system, you lost the index.
> Thank you for the consideration.

Have you tried using the compound file format introduced in 1.3?



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


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


Mime
View raw message