I’m using a SkipTransation callback in ShowHistory that does something like
$ttype = $Transaction->Type;
$$skip = 1 if (($_SkipSystemMessages) && ((($Transaction->Creator eq RT->Config->Get(‘SystemUserID’))
&& ($Transaction->Type ne ‘Status’)
&& ($Transaction->Type ne ‘Comment’)) || (($Transaction->Creator eq RT->Config->Get(‘CronUserID’))
&& (($Transaction->Type ne ‘Give’)
&& ($Transaction->Type ne ‘Correspond’))) || ($Transaction->Type eq ‘CustomField’) || ($Transaction->Type eq ‘Set’
&& $Transaction->Field eq ‘TimeWorked’)) );
my $type = $Transaction->Type;
But I guess it’s too late at this point for performance reasons, as we’re already processing the entry?
Orbis Support Manager
firstname.lastname@example.orgOn 7 Jun 2010, at 21:53, Kenneth Marshall wrote:
The last time I looked at this problem, the slow step is simply
preparing all of the transactions for the web. The biggest gains
were made by pruning the list of displayed transactions to the
bare minimum, by default. Then have a button to allow seeing
all of the transactions, if needed.
On Thu, Jun 03, 2010 at 09:27:45AM +0100, Justin Hayes wrote:
Does anyone have any suggestions on how to improve the time taken for RT to display ticket history. Depending on the number of entries on the ticket it can take 6-30seconds to render the ticket.
I’ve had a look in the mysql logs for slow queries and can’t see any (though it’s only logging ones that take longer than 1s so maybe it’s doing lots and lots of faster ones that can still be optimised).
I’ve put some debug logging in and all the time is going in ShowHistory, so I guess in the loop that loops over all the various transactions and things to display for that ticket.
Any suggestions or tweaks that people have done would be great, before I start investigating what’s going on at a lower level.