[rt-users] Performance problems on upgrade from 3.0 to 3.4 or 3.6.1

[Theo Kramer]

On Thu, 2007-01-04 at 12:17 -0500, Jesse Vincent wrote:
> 
> 
> On Thu, Jan 04, 2007 at 06:42:54PM +0200, Theo Kramer wrote:
<snip>
> > System Details as follows
> > 
> > O/S: Ubuntu Dapper
> > Database: MySQL 5.0.22
> 
> For kicks, cna you try mysql 4.1? I've had horrible problems with the
> braindead query optimizer on mysql 5.
> 
> 
<snip>

>>Problem Details as follows
> > 
> > The time taken to open/comment/reply to a ticket is way to high to be
> > useful - ie greater than 30 seconds. I did a bit of digging and looking
> > at mysql-slow.log discovered the following query
> > 
> > SELECT DISTINCT main.* FROM Users main , Principals Principals_1,  
> >   ACL ACL_2, CachedGroupMembers CachedGroupMembers_3
> > WHERE
> >   ((ACL_2.PrincipalId = CachedGroupMembers_3.GroupId)) AND
> >   ((ACL_2.PrincipalType = 'Group')) AND
> >   ((ACL_2.RightName = 'OwnTicket')) AND
> >   ((CachedGroupMembers_3.MemberId = Principals_1.id)) AND
> >   ((Principals_1.Disabled = '0')) AND
> >   ((Principals_1.PrincipalType = 'User')) AND
> >   ((Principals_1.id != '1')) AND
> >   ((main.id = Principals_1.id)) AND
> >   ((ACL_2.ObjectType = 'RT::Ticket' AND ACL_2.ObjectId   = 391495) OR
> >     (ACL_2.ObjectType = 'RT::Queue' AND ACL_2.ObjectId   = 11) OR
> >     (ACL_2.ObjectType = 'RT::System'))
> >   ORDER BY main.Name ASC;
> > 
> > 10 rows in set (36.72 sec)

Thanks Jesse - downgraded to mysql 4.1 and on exactly the same data and
exactly the same indexes get the following.

10 rows in set (0.32 sec)

which makes it viable.

So my conclusion is that mysql 5.0.22 is not viable for request-tracker
in our case.
 
-- 
Regards
Theo