So it all depends on your implementation and server restrictions. I'm just going to set it up with Tomcat to get it running "correctly" but I might just go with the native jetty server down the road when this is "for real".
On Thu, Aug 29, 2013 at 12:06 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 8/29/2013 12:08 PM, Jared Griffith wrote: > >> Is it more ideal to run the Jetty containers as opposed to running Tomcat >> with the Solr war? >> > > If I answer "yes" to that question, it's not really the whole story. Just > like the "vi vs. emacs" battle, it can become almost a religious debate. > Having said that, generally speaking, jetty is more ideal for Solr than > Tomcat. > > Jetty is the only container that receives official testing. Anytime > anyone runs Solr unit tests after checking out the source code, Jetty gets > tested. Tomcat only gets tested when users install Solr in it. Bugs > related to tomcat are sometimes found. They are relatively rare, but they > do happen. > > If a user really knows tomcat internals and how to tune it for specific > applications, they could probably make their tomcat Solr install run > circles around Jetty. > > The Jetty install that comes with Solr, in addition to being stripped of > all unnecessary features, has been lightly tuned so it works better with > Solr than a stock Jetty. It will have less memory overhead than a stock > Tomcat, because it's smaller. > > Thanks, > Shawn > > -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 <http://www.picsauditing.com> 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! <https://twitter.com/PICSAuditingLLC>
