My (our) query plugin uses specialized SolrCache's in lieu of the meta
data records. For each new searcher installed each fields possible
values will be determined and stored in a cache (off the top of my head,
some fields have a cardinality of well over 500k). Each time a query is
run that r
Solr is just a webapp that runs inside an appserver.
So it is up to the user to tune the JVM for the appserver.
Besides, client vs server mode, one can also tune the
heap size and garbage collection, as well as many many
other options of the JVM:
http://blogs.sun.com/roller/resources/watt/jvm-opti
Thanks Bill
So essentilly our webserver can make use of hotspot jvm if we configure our
webserver to it
And solr is just one of the webapplications running.
Got it
Rgds
Prabhu
On 4/3/06, Bill Au <[EMAIL PROTECTED]> wrote:
>
> Solr is just a webapp that runs inside an appserver.
> So it is up
Hey everybody ... sorry i'm getting into the discussion so late ... i was
in a Cloud Forrest in Costa Rica for 8 days -- plenty of Internet Cafe's,
but i avoided all of them.
First off, i wanted to point out that this discussion came up about a
month ago, and a lot of ideas about how to define c
: Seeing SolrServlet.java doPost and doGet, I thought I could call
: SolrCore execute() and update() methods without servlet container
: environment.
you can, in fact the SolrTest application does this (as will the JUnit
harness i'm hoping to get back to working on this weekend)...
http://svn.ap