Hi Nicola, I've just tried upgrading from 3.8.4 which I've been on for ages, on the hope that it would be better, but isn't.
So I don't think it's something that has either been introduced or fixed by 3.8.8. I'll take a look at that index though. Thanks, Justin ------------------------------------------------- Justin Hayes OpenBet Support Manager justin.ha...@openbet.com On 29 Jun 2010, at 15:49, Foggi, Nicola wrote: > > 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) > > Nicola > > -----Original Message----- > From: rt-users-boun...@lists.bestpractical.com on behalf of Justin Hayes > Sent: Tue 6/29/2010 9:28 AM > To: Jason Doran > Cc: rt Users > Subject: Re: [rt-users] Slow Ticket History 3.8.8 > > Thanks Jason - I'll give that a go as well. We have got a large DB (~10gb) so > keeping it tuned is definitely important. > > 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). > > Cheers, > > Justin > > ------------------------------------------------- > Justin Hayes > OpenBet Support Manager > justin.ha...@openbet.com > > On 29 Jun 2010, at 15:22, Jason Doran wrote: > > > Hi, > > If you are using mysqld have a look at "mysqltuner.pl" perl script (google) > > This has fixed quickly many performance issues on both RT and other > > web-based software we use. I run this every few weeks and apply suggested > > changes and then simply restart mysqld when things are quite. > > > > Regards, > > Jason Doran > > Computer Centre > > NUI, Maynooth > > > > On 29 Jun 2010, at 14:09, Justin Hayes wrote: > > > >> Hi everyone, > >> > >> I've raised this before, but we've had another look at it and still can't > >> see how to improve things. > >> > >> 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. > >> > >> We don't have any slow queries - all the time seems to be in the code > >> rendering the history of the ticket. > >> We've had a go at stripping functions out of ShowHistory, ShowTransaction > >> and ShowTransactionAttachmments but not had much success. > >> > >> FWIW our RT runs on quad 3ghz Xeons with 8gb of ram. > >> > >> 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. > >> > >> 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. > >> > >> <span>Time to display: 24.996907</span> > >> > >> Can anyone share some numbers from theirs for longer tickets? It would be > >> really appreciated. > >> > >> > >> Thanks, > >> > >> Justin > >> > >> ------------------------------------------------- > >> Justin Hayes > >> OpenBet Support Manager > >> justin.ha...@openbet.com > >> > >> > >> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > >> Buy a copy at http://rtbook.bestpractical.com > > > > >
Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
