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
