: > How big is your physical index directory on disk?
: It's about 2.9G now.
: Is there a direct connection between size of index and usage of ram?
Generally yes. Lucene loads a lot of your index into memory ... not
neccessarily the "stored" fields, but quite a bit of the index structure
needed f
Chris Hostetter wrote:
How big is your physical index directory on disk?
It's about 2.9G now.
Is there a direct connection between size of index and usage of ram?
Your best bet is to allocate as much ram to the server as you can.
Depending on how full your caches are, and what hitratios you ar
: The default value in the example installation is 3. Maybe
: it wolud be a good idea to increase this, too.
The example is really just designed to make it easy to see Solr in action
really fast ... not to demonstrate any recommended configuration of the
Jetty -- if we make too many tweaks to
: I'm currently testing a large index with more than 10 million
: documents and 24 fields, using the example installation with
: Jetty.
: When deleting or updateing documents from the index or doing
: search queries I get "Java heap space" error messages like
: this (in this case while trying to de
Yonik Seeley wrote:
>I think you are probably right about Jetty timing out the request.
>Solr doesn't implement timeouts for requests, and I havent' seen this
>behavior with Solr running on Resin.
>
>You could try another app server like Tomcat, or perhaps figure out of
>the Jetty timeout is config
