Hello,
If you are using Jetty, you don't have to dig very deep - just look for the
section about threads. Here is a snippet from Jetty 6.1.9's jetty.xml:
<Set name="ThreadPool">
<!-- Default bounded blocking threadpool
-->
<New class="org.mortbay.thread.BoundedThreadPool">
<Set name="minThreads">10</Set>
<Set name="maxThreads">50</Set>
<Set name="lowThreads">25</Set>
</New>
<!-- New queued blocking threadpool : better scalability
<New class="org.mortbay.thread.QueuedThreadPool">
<Set name="minThreads">10</Set>
<Set name="maxThreads">25</Set>
<Set name="lowThreads">5</Set>
<Set name="SpawnOrShrinkAt">2</Set>
</New>
-->
<!-- Optional Java 5 bounded threadpool with job queue
<New class="org.mortbay.thread.concurrent.ThreadPool">
<Set name="corePoolSize">50</Set>
<Set name="maximumPoolSize">50</Set>
</New>
-->
</Set>
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
> From: Lance Norskog <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Cc: "Norskog, Lance" <[EMAIL PROTECTED]>
> Sent: Tuesday, May 6, 2008 1:26:28 PM
> Subject: RE: Help optimizing
>
> One cause of out-of-memory is multiple simultaneous requests. If you limit
> the query stream to one or two simultaneous requests, you might fix this.
> No, Solr does not have an option for this. The servlet containers have
> controls for this that you have to dig very deep to find.
>
> Lance Norskog
>
> -----Original Message-----
> From: Grant Ingersoll [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 06, 2008 5:19 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Help optimizing
>
>
> On May 3, 2008, at 1:06 PM, Daniel Andersson wrote:
>
> > Hi (again) people
> >
> > We've now invested in a server with 8 GB of RAM after too many
> > OutOfMemory-errors.
> >
> > Our database/index is 3.5 GB and contains 4,352,471 documents. Most
> > documents are less than 1 kb. When performing a search, the results
> > vary between 1.5 seconds up to 60 seconds.
> >
> > I don't have a big problem with 1.5 seconds (even though below 1 would
> > be nice), but 60 seconds it just.. well, scary.
>
> Is this pure Solr time or overall application time? I ask, b/c it is often
> the case that people are measuring application time and the problem lies in
> the application, so I just want to clarify.
>
> Also, have you done any profiling to see where the hotspots are?
>
> -Grant
>
>
