On Fri, Sep 16, 2016 at 3:01 AM, <[email protected]> wrote: > 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.
If your "Trac queries" means Trac search feature, please try to use https://trac-hacks.org/wiki/TracAdvancedSearchPlugin. > 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? Prior to MySQL 5.6, FULLTEXT can be used with MyISAM. Trac requires database engine with transaction. Other databases don't understand MATCH...AGAINST. Then, Trac doesn't currently support it. -- Jun Omae <[email protected]> (大前 潤) -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
