al Message-
From: Shawn Heisey [mailto:s...@elyograg.org]
Sent: Tuesday, February 05, 2013 2:53 PM
To: solr-user@lucene.apache.org
Subject: Re: Really bad query performance for date range queries
On 2/5/2013 3:19 PM, Petersen, Robert wrote:
> Hi Shawn,
>
> I've looked at th
On 2/5/2013 3:19 PM, Petersen, Robert wrote:
Hi Shawn,
I've looked at the xing JVM before but don't use it. jHiccup looks like a
really useful tool. Can you tell us how you are starting it up? Do you start
it wrapping the app container (ie tomcat / jetty)?
Instead of just calling /usr/bin
[mailto:s...@elyograg.org]
Sent: Tuesday, February 05, 2013 1:27 PM
To: solr-user@lucene.apache.org
Subject: Re: Really bad query performance for date range queries
On 2/5/2013 12:51 PM, sausarkar wrote:
> We have a 96GB ram machine with 16 processors. the JVM is set to use 60 GB.
> The test that we
On 2/5/2013 12:51 PM, sausarkar wrote:
We have a 96GB ram machine with 16 processors. the JVM is set to use 60 GB.
The test that we are running are purely query there is no indexing going on.
I dont see garbage collection when I attach visualVM but see frequent CPU
spikes ~once every minute.
A
We have a 96GB ram machine with 16 processors. the JVM is set to use 60 GB.
The test that we are running are purely query there is no indexing going on.
I dont see garbage collection when I attach visualVM but see frequent CPU
spikes ~once every minute.
--
View this message in context:
http://l
On the surface, this doesn't seem right. Your corpus isn't very large and
it sounds like you have some significant hardware supporting it. I'm
guessing you have some other issues here like;
- inappropriate memory allocation
- too-frequent commits
- too many queries for your hardware
- indexing to t
Unfortunately we need data by minute we cannot go hour, is there an option
for 3 minutes or 5 minutes? something is like NOW/3MIN?
I am also noticing when I generating around 110 queries per second (date
range ones) after sometime solr does not respond and just freezes. Is there
a way to cure this
The core concept behind filter queries is that they cache their results
(list of documents) so that they can filter the main query more efficiently.
But is your query keeps changing, like every minute, the cached results need
to get thrown away and recalculated, every minute.
Can you try hourl
