>From my experience, you must hit some system issue. You should check disk
performance at first, disk queue length on Windows. Or you can enable gc
verbose to know the gc activities in details.
I designed auto upgrade mechanism in application by calling forceMerge(1),
to eradicate hybrid index for
There could be other applications running on the machine with 24 GB memory?
Which would result in total available memory less than what is required. In
this case there may be disk swap, which would take long time.
In theory, if you run this test on machines with memory 50 GB and 100 GB in
this case
The index will not change oftenly, so we call forceMerge in the end. Will
forceMerge(1) cost too much memory? And the final size of the index is 15GB. I
just want to know why different machine cost different time in forceMerge, them
have the same cpu and disk, but different size of memory. One
It is generally unnecessary to use forceMerge, that's a legacy from
older versions of Lucene/Solr.
Especially if the index is constantly changing, forceMerge generally
is both expensive and not
very useful.
These indexes must be huge though if any of them are taking 8 hours.
What's the background
GreetingsNow, i'm using lucene , the version is 4.10.3. For some reason, i
called forceMerge(1) in the end,and the final space of the Index Library is 15
GB. . But i found that forceMerge(1) cost a lot of time, and on different
machines ,the time differs. Is this caused by the different size o
