So you're right i did miss removing the app deployment but removing that still didn't really do that great. The avg request response time is still slower. The bell curve is a lot more streched than it was before but it doesn't seem to give an overall better performance.
Thanks for your suggestions, Tony On Wed, May 19, 2010 at 4:37 PM, Chris Hostetter <[email protected]>wrote: > > : "Switched" works for the specific setup i'm using - the server would > refer > : to itself in the CommonHttpSolrServer request sent, i.e. it would run > both > : the server and client sides. Removing this and simply using > : EmbeddedSolrServer just made the setup a little more sane in that aspect. > : Does that make more sense now? > > not really ... what *exactly* did you change about your setup and > your client code? please be specific -- how did you run solr > before when you were using CommonsHttpSolrServer? whare are *all* of the > steps you did when you switched to EmbeddedSolrServer (specificly: what > did the changes to your java client code look like, and what did you > hcange about how you "run" solr) > > Because if you still have the solr.war running in your servlet container, > and all you did is edit your java code to use EmbeddedSolrServer (poiting > at the same directory on disk) instead of COmmonsHttpSolrServer, thne you > are now running *two* instances of Solr in your VM, both reading from the > same indexes. > > > -Hoss > >
