Aaron Watters wrote: > > It looks to me like the Trac search functionality uses SQL "like". > I was wondering if anyone has seen performance issues with > this approach. Just testing using > > http://twistedmatrix.com/trac/search?q=the > > I get about 8000 documents, pretty quickly (which is probably > the whole database). So I guess performance would > degrade at sizes larger than that, if ever. > > My personal motivation for this musing is that I wrote > the NUCULAR full text retrieval package > > http://nucular.sourceforge.net > > and would love to see it used in Trac.
Hi Aaron, Yes, we're aware of this performance issue. There is a wiki page discussing how the search system could be improved: http://trac.edgewall.org/wiki/AdvancedSearch As far as I know nobody has started coding on this yet. And there are a few things that have to be decided before that can happen, for example if we should select a single indexer or use an abstraction layer (pyndexter[1] or some special type of plugins). [1]: http://swapoff.org/pyndexter btw, I noticed that according to the homepage nucular does not work on NTFS. This would be a show stopper for us. Do you have any info about when/if this will be solved? Cheers, Jonas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
