Hi Jan
Thanks for getting back to me. Here's the details:
JVM: jdk1.6.0_27
App Server: Tomcat 7
OS: Centos x86_64 5.4
RAM: 8GB
JVM RAM: 4GB
JVM ARGS: -Xms4G -Xmx4G -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
-XX:NewRatio=3 -XX:PermSize=128M -XX:MaxPermSize=256M
-Djava.util.logging.manager=org.apache
Hi,
Could you post more info about your environment?
OS, JVM version, Total RAM and how much allocated to JVM? JVM options such as
GC settings, other applications running on same box? document type and size,
size of your "index" folder on disk, schema & solrconfig changes (have you
migrated sc
Hi there
Yes I have tried that, and it makes a small difference but still getting the
slowdown, just slightly later.
No hints from the logs about the slowdown, no errors or useful info in there
even if I set all the logging on.
Willem
On Fri, Oct 7, 2011 at 2:38 PM, Jan Høydahl wrote:
> Hi,
>
Hi,
Have you tried to do a commit after the deleteByQuery only?
Also, what seems to cause the slowdown? Any hints from the logs?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
On 7. okt. 2011, at 10:04, Willem Basson wrote:
> Hi t
Hi there
We are currently moving from Solr 1.4 to 3.4 and we are seeing a few issues
with adding documents.
We do a delete by query and then do a lot of adds, about 100k before we do a
commit and optimise.
With 1.4 this was all fine, not super quick but didn't see any problems.
With 3.4 the rate o
