Does it need 10G to run? Have you cycled it down to, say, 4-5G as a
test? Large memory sizes can just cause more garbage collection.
What is the disk activity when this happens? Do you have paging turned
on? I generally turn it off- having things go into page-thrash mode is
lame.
How many searche
On Fri, Nov 19, 2010 at 12:01:09AM +, me said:
> I'm baffled - I've had way bigger indexes than this before with no
> performance problems. At first it was the frequent updates but the fact
> that it happens even when the indexer isn't running seems to put paid to
> that.
More information:
We currently have a 30G index with 73M of .tii files running on a
machine with 4 Intel 2.27GHz Xeons with 15G of memory.
About once a second a process indexes ~10-20 smallish documents using
the XML Update Handler. A commit happens after every update. However we
see this behaviour even if the i
