lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ariel <isaacr...@gmail.com>
Subject Re: Big problem with solr in an official server.
Date Mon, 19 Apr 2010 16:52:07 GMT
And what is the recommended max size memory I should use ??? Is there anyone
recommended ???
Regards.


On Mon, Apr 19, 2010 at 12:44 PM, Geek Gamer <geek4377@gmail.com> wrote:

> if you want to limit the use of memory by the java process you could use
> java -XmxNGB
> where N is the amount of memory you want to limit to jetty container.
>
> On Mon, Apr 19, 2010 at 10:05 PM, Ariel <isaacrc82@gmail.com> wrote:
>
> > I have just read the post, but it doesn't said if the problems with
> memory
> > are associated with that way, the jetty web server it is used when I
> start
> > solr that way, then I supposed that problems with memory should not
> happen
> > because jetty must administrate the way the memory is used.
> >
> > Then are you really sure I must migrate to a non jetty web server ??? It
> is
> > that what you recommend ?
> > Thanks in advance again.
> > Regards
> > Ariel
> >
> > On Mon, Apr 19, 2010 at 12:27 PM, Ahmet Arslan <iorixxx@yahoo.com>
> wrote:
> >
> > >
> > > > Hi everybody:
> > > >
> > > > I have a big problem with solr in a server with the memory
> > > > size it is using,
> > > > I am setting up Solr with "java -jar start.jar" command in
> > > > an ubuntu server,
> > > > the process start.jar is using 7Gb of  memory in the
> > > > server and it is
> > > > affecting considerably the performance of the server.
> > > > I would want to know how to configure it to use a limited
> > > > memory size with
> > > > high performance results, Do I need to migrate the solr to
> > > > an apache tomcat
> > > > servlet container to improve the memory performance ???
> > >
> > > Recent post about the "java -jar start.jar" :
> > > http://search-lucene.com/m/atxZc2MSKig2/run+in+background
> > >
> > >
> > >
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message