e settings
> that suit you best.
> Here's a few resources to help you get started:
> http://wiki.apache.org/lucene-java/ImproveSearchingSpeed
> https://wiki.apache.org/solr/SolrPerformanceProblems
> https://wiki.apache.org/solr/SolrPerformanceFactors
>
> On Mon,
the details of
> how the query was parsed, scored and how much time was taken by each module
> used by the request handler.
>
> On Mon, 15 Feb 2016, 10:42 Shahzad Masud <
> shahzad.ma...@northbaysolutions.net> wrote:
>
> > Please pardon my ignorance, but just wanted t
Please pardon my ignorance, but just wanted to check if there is anything
like explain plan while executing query on Solr. I have one query which is
taking a lot of time (56-68 seconds) with very huge network activity. While
most of queries are taking less than 4 seconds.
{!surround}
I have maske
uted+Request+Options
>
> Thanks,
> Susheel
>
> On Tue, Feb 9, 2016 at 12:10 AM, Shahzad Masud <
> shahzad.ma...@northbaysolutions.net> wrote:
>
> > Thank you Shawn for your response. I would be running some performance
> > tests lately on this structure (one JVM with m
nt size ranging from 100KB - 400 MB.
SM
On Mon, Feb 8, 2016 at 8:09 PM, Shawn Heisey wrote:
> On 2/8/2016 1:14 AM, Shahzad Masud wrote:
> > Thank you Shawn for your reply. Here is my structure of cores and shards
> >
> > Shard 1 = localhost:8983/solr_2014 [3 Core - Employ
-Dsolr.solr.home variable - which ends up pointing to one data
folder (2014 data) only.
Shahzad
On Thu, Feb 4, 2016 at 10:25 PM, Shawn Heisey wrote:
> On 2/4/2016 9:48 AM, Shahzad Masud wrote:
> > Thank you Shawn for your response. I have been using manual shards (old
> > mechanism) i.e. s
think this is a good design practise? Can you share an example which
may help me deploy two shards in one jetty?
Shahzad
On Thursday, 4 February 2016, Shawn Heisey wrote:
> On 2/4/2016 7:29 AM, Shahzad Masud wrote:
> > Q: Is this a normal that one node support one shard in Jetty?
> >
I have been running Solr 4.10 with Tomcat 7 with manual shard scheme (i.e.
4 Tomcats with 16 shards - Each tomcat having 4 contexts / instances in it
to represent shards). It was working fairly good for last 4 years, but with
few OOM (Out of memory) on random servers. This situation get back normal
