production solr - app server choice ?

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

production solr - app server choice ?

rubdabadub
Hi:

I am wondering what everyone is using when it comes to app server i.e.
Jetty, Resin, Tomcat etc. I have seen the wiki pages .. seems like in
Resin you can setup multiple solr-app (Ryan are you doing this? Sorry
I don't know enough to know what is the benefit of such setup).

What about SUN's glassfish? anyone tried that with Solr? it feels and
looks very glossy :-)

Any specific thing I should look for when testing various app servers.
The site is a local portal and the traffic is very high and I am not
sure if Jetty is enough maybe it is..

Kind Regards
Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

Erik Hatcher
We use jetty on a few applications with no problem.  I recommend it  
unless and until you outgrow it (but I doubt you will).   Resin, in  
my past experience with it, is fantastic.  But no need to even go  
there until you outgrow Jetty I don't think.  lucenebook.com, for  
example, is entirely driven by Jetty.

        Erik


On Mar 9, 2007, at 5:10 AM, rubdabadub wrote:

> Hi:
>
> I am wondering what everyone is using when it comes to app server i.e.
> Jetty, Resin, Tomcat etc. I have seen the wiki pages .. seems like in
> Resin you can setup multiple solr-app (Ryan are you doing this? Sorry
> I don't know enough to know what is the benefit of such setup).
>
> What about SUN's glassfish? anyone tried that with Solr? it feels and
> looks very glossy :-)
>
> Any specific thing I should look for when testing various app servers.
> The site is a local portal and the traffic is very high and I am not
> sure if Jetty is enough maybe it is..
>
> Kind Regards

Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

rubdabadub
Thanks Erik!

On 3/9/07, Erik Hatcher <[hidden email]> wrote:
> We use jetty on a few applications with no problem.  I recommend it
> unless and until you outgrow it (but I doubt you will).   Resin, in
> my past experience with it, is fantastic.  But no need to even go
> there until you outgrow Jetty I don't think.  lucenebook.com, for
> example, is entirely driven by Jetty.

Is it the collex/nine where you have more then 4 mill docs you are
using jetty? I
have a lot of docs i.e. 20 mil and it has bunch of fields i.e 25 per
doc this is why i worry..
but i dont think my qps will  as high as I hoped so jetty should be just fine.

Thanks again for your help.

> On Mar 9, 2007, at 5:10 AM, rubdabadub wrote:
>
> > Hi:
> >
> > I am wondering what everyone is using when it comes to app server i.e.
> > Jetty, Resin, Tomcat etc. I have seen the wiki pages .. seems like in
> > Resin you can setup multiple solr-app (Ryan are you doing this? Sorry
> > I don't know enough to know what is the benefit of such setup).
> >
> > What about SUN's glassfish? anyone tried that with Solr? it feels and
> > looks very glossy :-)
> >
> > Any specific thing I should look for when testing various app servers.
> > The site is a local portal and the traffic is very high and I am not
> > sure if Jetty is enough maybe it is..
> >
> > Kind Regards
>
>
Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

Bertrand Delacretaz
In reply to this post by rubdabadub
On 3/9/07, rubdabadub <[hidden email]> wrote:

> ...I am wondering what everyone is using when it comes to app server i.e.
> Jetty, Resin, Tomcat etc....

I suspect that asking four people might give you five different
answers on this one ;-)

Whichever servlet container you use, IMHO the important thing is to
learn to know how to tune it according to your needs, traffic
patterns, hardware and software environment, etc.

-Bertrand
Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

jrodenburg
We're running solr with multiple webapps under Tomcat 5.5.17, runs fine.  We
have it deployed on FC5, FC6 and RHEL4 distros.  Works the same on all of
them, no blocking issues.

From a general perspective, Bertrand is correct: go with what you know as
long as it meets your needs.


On 3/9/07, Bertrand Delacretaz <[hidden email]> wrote:

>
> On 3/9/07, rubdabadub <[hidden email]> wrote:
>
> > ...I am wondering what everyone is using when it comes to app server i.e
> .
> > Jetty, Resin, Tomcat etc....
>
> I suspect that asking four people might give you five different
> answers on this one ;-)
>
> Whichever servlet container you use, IMHO the important thing is to
> learn to know how to tune it according to your needs, traffic
> patterns, hardware and software environment, etc.
>
> -Bertrand
>
Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

Erik Hatcher
In reply to this post by rubdabadub

On Mar 9, 2007, at 6:46 AM, rubdabadub wrote:
> On 3/9/07, Erik Hatcher <[hidden email]> wrote:
>> We use jetty on a few applications with no problem.  I recommend it
>> unless and until you outgrow it (but I doubt you will).   Resin, in
>> my past experience with it, is fantastic.  But no need to even go
>> there until you outgrow Jetty I don't think.  lucenebook.com, for
>> example, is entirely driven by Jetty.
>
> Is it the collex/nine where you have more then 4 mill docs you are
> using jetty?

No.... at NINES - http://www.nines.org/collx - we have just over 60k  
documents currently (see the number in the footer).  The index of the  
UVa library (3.7M records) is not currently deployed other than on my  
laptop.

The number of documents shouldn't matter as far as what app server  
you use.  Though I'm not really sure what the variables would be in  
determining which app. server is best with Solr.  I don't think  
you'll go wrong with Jetty, Tomcat, or Resin - all will respond from  
Solr quite rapidly provided you take care of the core Solr caching  
concerns and set the JVM properties with enough heap and such to  
operate smoothly.

> I
> have a lot of docs i.e. 20 mil and it has bunch of fields i.e 25 per
> doc this is why i worry..
> but i dont think my qps will  as high as I hoped so jetty should be  
> just fine.

Testing is the best way to find out, and its fairly easy to switch  
app. servers and re-test.  Again, I'd be surprised if the choice of  
app. server has much relation to performance in your case.

        Erik



Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

Bertrand Delacretaz
In reply to this post by rubdabadub
On 3/9/07, rubdabadub <[hidden email]> wrote:

> ...The site is a local portal and the traffic is very high and I am not
> sure if Jetty is enough maybe it is....

Just an additional note on this: asking four people about what "very
high" traffic means might also give you five different answers ;-)

FWIW, I've been testing Solr on the plain Jetty example config at more
than 100 semi-random queries per second and it ran just fine, on a
medium-range server (dual Xeon 2Ghz IIRC).

But this is with our data and our type of queries - I agree with Erik
that testing is the only way to find out how your setup will perform
with your own data and queries.

Simply generating a lot of semi-random requests from a collection of
possible query parameters, and feeding the resulting URLs to multiple
instances of curl or wget to generate some load, will tell you a lot
about how your setup performs, and where the hotspots are.

-Bertrand
Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

James liu-2
I use jetty and tomcat 6 under win2003.

They all work well.




2007/3/10, Bertrand Delacretaz <[hidden email]>:

>
> On 3/9/07, rubdabadub <[hidden email]> wrote:
>
> > ...The site is a local portal and the traffic is very high and I am not
> > sure if Jetty is enough maybe it is....
>
> Just an additional note on this: asking four people about what "very
> high" traffic means might also give you five different answers ;-)
>
> FWIW, I've been testing Solr on the plain Jetty example config at more
> than 100 semi-random queries per second and it ran just fine, on a
> medium-range server (dual Xeon 2Ghz IIRC).
>
> But this is with our data and our type of queries - I agree with Erik
> that testing is the only way to find out how your setup will perform
> with your own data and queries.
>
> Simply generating a lot of semi-random requests from a collection of
> possible query parameters, and feeding the resulting URLs to multiple
> instances of curl or wget to generate some load, will tell you a lot
> about how your setup performs, and where the hotspots are.
>
> -Bertrand
>



--
regards
jl
Reply | Threaded
Open this post in threaded view
|

Re: production solr - app server choice ?

rubdabadub
Thanks for the feedback! I was planning to test but I wanted to know what
other were using. I have been using tomcat extensively but got tired of it (no
technical reason).

Jetty sounds too simple so I thought I ask :-) Never tried Resin but it has some
good reputation.

The local portal is using tomcat and it serves approximately 20 req/ second in
peak times. I don't know how high load is this as I have no other
reference. I know for
sure the local portal is no google :-)

I think as Erik mentioned its probably Solr config that will increase
or decrease performance.
I am currently reading up/testing performance pages. Any other advice
is always welcome.

Thanks again for all the input.

On 3/10/07, James liu <[hidden email]> wrote:

> I use jetty and tomcat 6 under win2003.
>
> They all work well.
>
>
>
>
> 2007/3/10, Bertrand Delacretaz <[hidden email]>:
> >
> > On 3/9/07, rubdabadub <[hidden email]> wrote:
> >
> > > ...The site is a local portal and the traffic is very high and I am not
> > > sure if Jetty is enough maybe it is....
> >
> > Just an additional note on this: asking four people about what "very
> > high" traffic means might also give you five different answers ;-)
> >
> > FWIW, I've been testing Solr on the plain Jetty example config at more
> > than 100 semi-random queries per second and it ran just fine, on a
> > medium-range server (dual Xeon 2Ghz IIRC).
> >
> > But this is with our data and our type of queries - I agree with Erik
> > that testing is the only way to find out how your setup will perform
> > with your own data and queries.
> >
> > Simply generating a lot of semi-random requests from a collection of
> > possible query parameters, and feeding the resulting URLs to multiple
> > instances of curl or wget to generate some load, will tell you a lot
> > about how your setup performs, and where the hotspots are.
> >
> > -Bertrand
> >
>
>
>
> --
> regards
> jl
>