Apache

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • addIndexes getting slower and slower plus eating up Mem

    1 answers - 677 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    The answer is because addIndexes() currently always does an optimize post-merge. If I recall correctly optimize() will create a complete copy of the existing index during the optimize process then delete the old one so this shouldn't be done too often.
    of interest, why are you using a RAMDirectory here? An IndexWriter uses one internally of size IndexWriter.setMaxBufferedDocs so you get the benefits of buffering automatically when writing to a File-based directory.
    Cheers
    Mark
    To unsubscribe, e-mail: java-user-unsubscribe (AT) lucene (DOT) apache.org
    For additional commands, e-mail: java-user-help (AT) lucene (DOT) apache.org
  • No.1 | | 402 bytes | |

    Hy,

    Friday 07 July 2006 12:23 mark harwood wrote:
    of interest, why are you using a RAMDirectory here? An IndexWriter uses
    one internally of size IndexWriter.setMaxBufferedDocs so you get the
    benefits of buffering automatically when writing to a File-based directory.
    realy? I read the trick here and so I did it. I'll try without it to see if
    its a difference!

    Thanks

Re: addIndexes getting slower and slower plus eating up Mem


max 4000 letters.
Your nickname that display:
In order to stop the spam: 9 + 9 =
QUESTION ON "Apache"

EMSDN.COM