+1...because the best way to manage the system resources (memory, cpu, etc.) in a enviroment that involves Solr is in having an isolated Solr server that doesn't interfere with resources demanded by other web applications; this is the case of large Solr indexes...of course that you can achieve that installing a servlet container for Solr (only!)...and that's not very different to run Solr as a separate service.
On Tue, May 7, 2013 at 4:48 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 5/7/2013 8:02 AM, Ariel Zerbib wrote: > > It also means that it will be necessary to run 2 big JVMs on the same > > server or to have 2 servers. You need to take it in account; do you > > really want to force to run solr standalone as a database? > > We are always telling people that Solr works best when it is the only > thing that runs on the server. Solr loves resources, and if something > else is using them, it won't perform as well. > > Typically the amount of heap memory required for your servlet container > and the JVM is nothing compared to Solr itself, so if you can remove > Solr from your web server container, you can reduce the size of that > JVM. That will free up system memory for use with Solr. To be > perfectly frank here, if your memory is so tight that this will be a > problem, then your server is undersized and performance problems with > Solr are inevitable. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
