<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7655.8">
<TITLE>RE: [rt-users] Slow Ticket History 3.8.8</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>I did just have a problem with 3.8.8 and one of the indexes (didn't have the problem on 3.8.6 or below). It turned out to be the index GROUPS2 on the Groups table... dropped the index, and performance was back to normal (pre 3.8.8)<BR>
<BR>
Nicola<BR>
<BR>
-----Original Message-----<BR>
From: rt-users-bounces@lists.bestpractical.com on behalf of Justin Hayes<BR>
Sent: Tue 6/29/2010 9:28 AM<BR>
To: Jason Doran<BR>
Cc: rt Users<BR>
Subject: Re: [rt-users] Slow Ticket History 3.8.8<BR>
<BR>
Thanks Jason - I'll give that a go as well. We have got a large DB (~10gb) so keeping it tuned is definitely important.<BR>
<BR>
However as stated the time seems to be lost in code, after I'd have thought it had run the query for the ticket (though I may be wrong in that assumption).<BR>
<BR>
Cheers,<BR>
<BR>
Justin<BR>
<BR>
-------------------------------------------------<BR>
Justin Hayes<BR>
OpenBet Support Manager<BR>
justin.hayes@openbet.com<BR>
<BR>
On 29 Jun 2010, at 15:22, Jason Doran wrote:<BR>
<BR>
> Hi,<BR>
> If you are using mysqld have a look at "mysqltuner.pl" perl script (google)<BR>
> This has fixed quickly many performance issues on both RT and other<BR>
> web-based software we use. I run this every few weeks and apply suggested<BR>
> changes and then simply restart mysqld when things are quite.<BR>
><BR>
> Regards,<BR>
> Jason Doran<BR>
> Computer Centre<BR>
> NUI, Maynooth<BR>
><BR>
> On 29 Jun 2010, at 14:09, Justin Hayes wrote:<BR>
><BR>
>> Hi everyone,<BR>
>><BR>
>> I've raised this before, but we've had another look at it and still can't see how to improve things.<BR>
>><BR>
>> We put a lot of comments/replies in our tickets. Often there can be 50-100 entries in a ticket, mostly plain text. Loading such a ticket can take 10-20secs.<BR>
>><BR>
>> We don't have any slow queries - all the time seems to be in the code rendering the history of the ticket.<BR>
>> We've had a go at stripping functions out of ShowHistory, ShowTransaction and ShowTransactionAttachmments but not had much success.<BR>
>><BR>
>> FWIW our RT runs on quad 3ghz Xeons with 8gb of ram.<BR>
>><BR>
>> I'd like to try and determine if we're just slow, or if this is just how long RT takes. Maybe perl is just slow.<BR>
>><BR>
>> Can anyone shed any light on how long it takes them to render long tickets in their systems? If you look at the page source it gives you a value e.g.<BR>
>><BR>
>> <span>Time to display: 24.996907</span><BR>
>><BR>
>> Can anyone share some numbers from theirs for longer tickets? It would be really appreciated.<BR>
>><BR>
>><BR>
>> Thanks,<BR>
>><BR>
>> Justin<BR>
>><BR>
>> -------------------------------------------------<BR>
>> Justin Hayes<BR>
>> OpenBet Support Manager<BR>
>> justin.hayes@openbet.com<BR>
>><BR>
>><BR>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.<BR>
>> Buy a copy at <A HREF="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</A><BR>
><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>