Ok. a change in recent (Since august) DBIx::SearchBuilders caused RT to
_totally_ lose on indices with mysql. I just rolled 0.46-test1 in
ftp://ftp.fsck.com/pub/rt/devel
My quick benchmarking:
On a 150,000 ticket database (Yes, that's one hundred and fifty thousand
tickets)
Before the new DBIx::SearchBuilder, any nontrivial search of tickets took over
a minute and display of a single ticket took 15 seconds.
Now, the same search takes between 1 and 30 seconds (full text searches still
suck) and display of a single ticket takes 1 second. I suspect that the "right" fix for postgres is to convert the indices to indices on lower(colname).
--
http://www.bestpractical.com/products/rt -- Trouble Ticketing. Free.
_totally_ lose on indices with mysql. I just rolled 0.46-test1 in
ftp://ftp.fsck.com/pub/rt/devel
My quick benchmarking:
On a 150,000 ticket database (Yes, that's one hundred and fifty thousand
tickets)
Before the new DBIx::SearchBuilder, any nontrivial search of tickets took over
a minute and display of a single ticket took 15 seconds.
Now, the same search takes between 1 and 30 seconds (full text searches still
suck) and display of a single ticket takes 1 second. I suspect that the "right" fix for postgres is to convert the indices to indices on lower(colname).
--
http://www.bestpractical.com/products/rt -- Trouble Ticketing. Free.