A while back (approximately 16-24 months ago) we installed RT 3.0.1,
with MySQL as the database engine.
Subsequently we experienced some of the performance problems
which at the time were occurring with that version when MySQL and
Apache were not tuned properly after the RT upgrade or install.
This engendered much unpleasantness among the staff using RT here,
leading to frenzied efforts to find a rapid fix.
So, after a reading some posts to this list recommending it, I converted
RT’s tables from InnoDB to MyISAM. The table type for our RT install has
remained MyISAM ever since.
The best thing that I can say about this fix is that it didn’t make
and in any case, after employing additional measures we eventually
the sort of performance originally anticipated.
However, we are now committed to upgrading RT to the latest version.
While making this upgrade, plainly we should get back on the right foot
to the MySQL table type that RT prefers (or perhaps now requires) and so
I have two
questions for the list:
- Will the database upgrade scripts to be run after “make upgrade” , e.g.,
/opt/rt3/sbin/rt-setup-database --action schema
automatically convert from MyISAM to InnoDB?
- If not, has anyone any advice or caveats about effecting such a
conversion using the mysql client?
Web Programmer/Assistant Unix Administrator
College of Art and Sciences, Educational Technology
414 Clemens Hall