Re: Performance issues with CursorMark

2020-10-26 Thread Erick Erickson
pta >> Sent: Monday 26th October 2020 17:00 >> To: solr-user@lucene.apache.org >> Subject: Re: Performance issues with CursorMark >> >> Hey Markus, >> >> What are you sorting on? Do you have docValues enabled on the sort field ? >> >> On Mon, Oct

RE: Performance issues with CursorMark

2020-10-26 Thread Markus Jelsma
> Sent: Monday 26th October 2020 17:00 > To: solr-user@lucene.apache.org > Subject: Re: Performance issues with CursorMark > > Hey Markus, > > What are you sorting on? Do you have docValues enabled on the sort field ? > > On Mon, Oct 26, 2020 at 5:36 AM Markus Jelsma >

Re: Performance issues with CursorMark

2020-10-26 Thread Anshum Gupta
Hey Markus, What are you sorting on? Do you have docValues enabled on the sort field ? On Mon, Oct 26, 2020 at 5:36 AM Markus Jelsma wrote: > Hello, > > We have been using a simple Python tool for a long time that eases > movement of data between Solr collections, it uses CursorMark to fetch >

Re: performance issues with geofilt

2015-02-25 Thread david.w.smi...@gmail.com
Okay. Just to re-emphasize something I said but which may not have been clear, it isn’t an either-or for filter & sort. Filter with the spatial field type that makes sense for filtering, sort (or boost) with the spatial field type that makes sense for sorting. RPT sucks for distance sorting, Lat

Re: performance issues with geofilt

2015-02-24 Thread david.w.smi...@gmail.com
Hi Dirk, The RPT field type can be used for distance sorting/boosting but it’s a memory pig when used as-such so don’t do it unless you have to. You only have to if you have a multi-valued point field. If you have single-valued, use LatLonType specifically for distance sorting. Your sample quer

Re: Performance issues with facets and filter query exclusions

2014-07-18 Thread Hayden Muhl
That query is representative of some of the queries in my test, but I didn't notice any correlation between using the match all docs query and poor query performance. Here's another example of a query that took longer than expected. qt=en&q=dress green leather&fq=userId:(383)&fq={!tag=productR

Re: Performance issues with facets and filter query exclusions

2014-07-18 Thread Yonik Seeley
On Fri, Jul 18, 2014 at 2:10 PM, Hayden Muhl wrote: > I was doing some performance testing on facet queries and I noticed > something odd. Most queries tended to be under 500 ms, but every so often > the query time jumped to something like 5000 ms. > > q=*:*&fq={!tag=productBrandId}productBrandId:

Re: Performance issues

2011-11-20 Thread Erick Erickson
Please review: http://wiki.apache.org/solr/UsingMailingLists Best Erick On Sun, Nov 20, 2011 at 5:32 AM, Tor Henning Ueland wrote: > On Sun, Nov 20, 2011 at 11:27 AM, Lalit Kumar 4 wrote: >> >> The search with couple of parameters bringing 650 counts(out of 2500 approx) >> and taking around 3

Re: Performance issues

2011-11-20 Thread Tor Henning Ueland
On Sun, Nov 20, 2011 at 11:27 AM, Lalit Kumar 4 wrote: > > The search with couple of parameters bringing 650 counts(out of 2500 approx) > and taking around 30 seconds > The schema.xml have more than 100 fields. You have of course started with the basics like making sure that the index is less th

Re: Performance issues

2011-11-20 Thread Lalit Kumar 4
"solr-user@lucene.apache.org" Cc: solr-user@lucene.apache.org Subject: Re: Performance issues http://www.lucidimagination.com/content/scaling-lucene-and-solr Has good guidance. Wrt 1. What is the issue - mem, cpu or query perf or indexing process On Nov 20, 2011, at 11:39 AM, Lalit Kuma

Re: Performance issues

2011-11-20 Thread Govind @ Gmail
http://www.lucidimagination.com/content/scaling-lucene-and-solr Has good guidance. Wrt 1. What is the issue - mem, cpu or query perf or indexing process On Nov 20, 2011, at 11:39 AM, Lalit Kumar 4 wrote: > Hello: > We recently have seen performance issues of SOLR (running on jetty). > > W

Re: Performance issues when querying on large documents

2010-07-24 Thread Erick Erickson
What are you returning? I'd be quite surprised if it was the search, so first I'd look elsewhere. In particular, are you returning all 1,000 pages? What happens if you specify returning a small field (the fl= parameter). Also, look at the debug output of the query, it breaks down the various phase

Re: Performance issues when querying on large documents

2010-07-24 Thread dc tech
Are you storing the full 1,000 pages in the index? If so, that is probably not helping either. On 7/23/10, ahammad wrote: > > Hello, > > I have an index with lots of different types of documents. One of those > types basically contains extracts of PDF docs. Some of those PDFs can have > 1000+ pag

Re: Performance issues when querying on large documents

2010-07-23 Thread Alexey Serba
Do you use highlighting? ( http://wiki.apache.org/solr/HighlightingParameters ) Try to disable it and compare performance. On Fri, Jul 23, 2010 at 10:52 PM, ahammad wrote: > > Hello, > > I have an index with lots of different types of documents. One of those > types basically contains extracts o

Re: Performance-Issues and raising numbers of "cumulative inserts"

2010-02-16 Thread Antonio Lobato
ave to look elsewhere to fix the problem. Anyone an idea what could cause the increasing warmup-Times? If required I can post some stats. Thanking you in anticipation! Regards, Sven Feed: Solr-Mailing-List Bereitgestellt am: Dienstag, 16. Februar 2010 09:05 Autor: Shalin Shekhar Manga

Re: Performance-Issues and raising numbers of "cumulative inserts"

2010-02-16 Thread Lance Norskog
he increasing warmup-Times? If required I > can post some stats. > > > > Thanking you in anticipation! > > > > Regards, > > Sven > > > > Feed: Solr-Mailing-List > Bereitgestellt am: Dienstag, 16. Februar 2010 09:05 > Autor: Shalin Shekhar Man

Re: Performance-Issues and raising numbers of "cumulative inserts"

2010-02-16 Thread Shalin Shekhar Mangar
On Tue, Feb 16, 2010 at 1:06 PM, Bohnsack, Sven wrote: > Hey IT-Crowd! > > I'm dealing with some performance issues during warmup the > queryResultCache. Normally it tooks about 11 Minutes (~700.000 ms), but > now it tooks about 4 MILLION and more ms. All I can see in the solr.log > ist that the