Well, I guess I’ll have to upgrade MySQL to support InnoDB tables then!
Thanks for the help! Jesse, it’s a compliment to you and your work on
RT that I’m going through this much pain to upgrade to rt3! If you
have a minute, could you point out to us listers the best way to support
LDAP with rt3? That should probably be in the docs that get released
Thanks again, and great job on rt3! It rocks!
/MikeFrom: Jesse Vincent [mailto:firstname.lastname@example.org]
Sent: Thursday, March 13, 2003 4:50 PM
To: Michael K. Brown
Subject: Re: [rt-users] rt-2-1-85: mysql performance ?
Is there any way to improve the performance?
New install of rt3, import of dumpfile via the 1.5 version of import
script. MySQL 3.23.45, perl 5.8, all dependencies satisfied.
Well, not exactly all dependencies. RT3 requires InnoDB tables if
you’re using mysql. You’re very clearly using MyISAM tables. There’s a
massive performance hit when you use MyIASM tables. And since they don’t
support row-level locking, one bad query will hurt everyone.
Table Records Type Size
ACL 64 MyISAM 8.9 KB
Attachments 2,238 MyISAM 3.7 MB
CachedGroupMembers 8,107 MyISAM 748.4 KB
CustomFieldValues 325 MyISAM 23.2 KB
CustomFields 21 MyISAM 4.4 KB
GroupMembers 2,651 MyISAM 93.7 KB
Groups 3,129 MyISAM 442.8 KB
Links 83 MyISAM 28.7 KB
Principals 3,453 MyISAM 130.4 KB
Queues 3 MyISAM 4.4 KB
ScripActions 15 MyISAM 3.7 KB
ScripConditions 9 MyISAM 2.9 KB
Scrips 22 MyISAM 6.6 KB
Templates 9 MyISAM 5.0 KB
TicketCustomFieldValues 2,532 MyISAM 146.5 KB
Tickets 695 MyISAM 149.7 KB
Transactions 8,005 MyISAM 628.2 KB
Users 323 MyISAM 97.1 KB
sessions 1 MyISAM 9.9 KB
19 table(s) 31,685 – 6.1 MB
http://www.bestpractical.com/rt – Trouble Ticketing. Free.