We have been analyzing (slow) performance of Trac queries, with 160K+ tickets and 100 users. We have been experiencing Trac queries taking 45 seconds and longer to update browser screens. One option we would like to explore is that addition of FULLTEXT index in InnoDB storage engine in MySQL. Your documentation seems somewhat dated 6 or 7 years ago), where it claims that FULLTEXT is only available for MyISAM (which has very slow performance) in MySQL. There have been enhancements to MySQL in intervening years.
To the best of my understanding, to "trigger" use of such FULLTEXT indices, one has to alter the SQL query: using MATCH... AGAINST... construct, instead of LIKE. When I look into DEBUG logs from Trac, and when I scan the almost 100KLOC .py* code in Trac, I only see queries composed of SELECT...LIKE..., and nothing looking like MATCH... AGAINST... Are there code changes that have to be made to use FULLTEXT indices in MySQL? Is there some kind of "switch" or "patch" to implement such changes? p.s. I get the impression that MATCH... AGAINST... is not traditional SQL (certainly not in '92 or '99 standards?). Is it supported by other databases? Is it supported by Trac? -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
