Hey, David. How are you? I did what you suggested and now works fine. However I hope that those performance issues will be resolved soon and I hope I could help some way: coding, testing, whatever. About cache warm up, I have setted up some warm-up queries in solrconfig.xml that fills the cache. One last question! The "d" parameter aswell as the "score" are measured in degrees, right?
Thank you very much for your feedback. Regards, - Luis Cappa 2013/3/9 David Smiley (@MITRE.org) <dsmi...@mitre.org> > Rakudten wrote > > Hello again! > > > > Uhm, so if I have understood then if I´m writing/reading from the index > at > > the same time (in other words, indexing operations are executing at the > > same that that other ones are querying) the performance goes down, isn´t > > it? > > Committing is the problem (soft or hard) due to the subsequent warmup of > the > point cache, not adding/indexing data. > > > Rakudten wrote > > Refering to the fieldType that I´m using, I´m just testing and I just > want > > to implement the classic scenario where each document has one coordinate > > and to which execute geo spatial queries "given a circle with X radius". > I > > was testing with a multiValued field because I was wondering to include > > one > > or more coordinates for each document due to the requirements of the > > project that I´m developing: I´m tracking users positions until a top of > N > > positions (coordinates) to be stored in that multiValued field, but I can > > adapt into just one coordinate per user if that change gets a better > > performance. > > > > In other words, David, and to summary: > > > > - I just one to implement the classic scenario "coordinate + circle + > > radius X". > > > > - Due to NRT user position changes, I will write & read into the index > > continuosly. > > > > - I was testing with that fieldType multiValued, but I can change it into > > another fieldType and into a single value field type if that improves > > performance. In that case, what would you recommend? > > Is it good enough sort by the most recent point only? You could still > filter by all points if you want. Spatial sorting & filtering are > currently > independent. So I suggest using not only the fieldType you have there but > also LatLonType for the latest position that you want to sort on. > Configure > it (via coordinate_ field type) to use floats instead of doubles. > > > Rakudten wrote > > - If even changing fieldTypes, multiValues or not, etc. the performance > > doesn´t improves, what other alternatives would you recommend me to use? > > I´m a Solr lover from Solr 1.4 version, but I´m familiar to other Spatial > > Search alternatives technologies/tools/dbs like MongoDB. Any suggestions > > or > > recommendations? > > Solr should be fine. > > Cheers, > David > > > > ----- > Author: > http://www.packtpub.com/apache-solr-3-enterprise-search-server/book > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-4-1-problems-with-Spatial-Search-tp4044868p4046004.html > Sent from the Solr - User mailing list archive at Nabble.com. >
