Markus, It's hard to suggest anything until you provide a profiler snapshot which says what it spends time in prepare for. As far as I know in prepare it parses queries e.g. we have a really heavy query parsers, but I don't think it's really common.
On Mon, Nov 19, 2012 at 3:08 PM, Markus Jelsma <markus.jel...@openindex.io>wrote: > I'd also like to know which parts of the entire query constitute the > prepare time and if it would matter significantly if we extend the edismax > plugin and hardcode the parameters we pass into (reusable) objects. > > Thanks, > Markus > > -----Original message----- > > From:Markus Jelsma <markus.jel...@openindex.io> > > Sent: Fri 16-Nov-2012 15:57 > > To: solr-user@lucene.apache.org > > Subject: Reduce QueryComponent prepare time > > > > Hi, > > > > We're seeing high prepare times for the QueryComponent, obviously due to > the vast amount of field and queries. It's common to have a prepare time of > 70-80ms while the process times drop significantly due to warmed searchers, > OS cache etc. The prepare time is a recurring issue and i'd hope if there > are people here that can share some thoughts or hints. > > > > We're using a recent check out on a 10 node test cluster with SSD's > (although this is no IO issue) and edismax on about a hundred different > fields, this includes phrase searches over most of those fields and > SpanFirst queries on about 25 fields. We'd like to see how we can avoid > doing the same prepare procedure over and over again ;) > > > > Thanks, > > Markus > > > -- Sincerely yours Mikhail Khludnev Principal Engineer, Grid Dynamics <http://www.griddynamics.com> <mkhlud...@griddynamics.com>
