[Xapian-tickets] [Xapian] #679: Memory and speed issues in wildcard searches

[Xapian]

#679: Memory and speed issues in wildcard searches
-------------------------+--------------------------
 Reporter:  dk           |             Owner:  olly
     Type:  defect       |            Status:  new
 Priority:  normal       |         Milestone:
Component:  QueryParser  |           Version:  1.3.2
 Severity:  normal       |        Resolution:
 Keywords:               |        Blocked By:
 Blocking:               |  Operating System:  All
-------------------------+--------------------------

Comment (by olly):

 If you're using GCC, you could try telling its STL not to pool memory by
 setting this environment variable:

 {{{
 export GLIBCXX_FORCE_NEW=1
 }}}

 However, it pools by default for performance reasons, so this might make
 things slower.

 Perhaps we should have a custom allocator for cursor blocks - those used
 for running a match should be released once that match has completed, so
 it shouldn't be very complex to track which blocks are used.

 The Perl bindings have a hard-coded list of constants to export currently
 - you should be able to just use the full name though - e.g.
 `Xapian::Query::WILDCARD_LIMIT_FIRST`.

--
Ticket URL: <http://trac.xapian.org/ticket/679#comment:7>
Xapian <http://xapian.org/>
Xapian