[rt-users] Handling a ticket that contains MANY comments

[Tim Cutts]

On 22 Apr 2011, at 15:44, rt-users-request at lists.bestpractical.com wrote:

> Hello all,
> 
> Question:  How should I best handle a ticket with multiple comments?  By multiple, I mean 400+.
> 
> Here's the background.  Our helpdesk had to deal w/ a widespread outage.  Tons upon tons of ppl were calling in for the entire day.  They decided they needed to log all these calls, so they created on ticket, named for this example "outage".  Everytime someone called in, they would open the "outage" ticket and put a quick "advised user of outage" in the ticket.  However, once the ticket started growing into the hundreds of comments, it would nearly lock the server up when someone would access it.  The CPU would peg out while the page was loaded, which would take roughly 2 minutes... and with probably a new person trying to access the ticket every 15 seconds, you could see how this was a problem.  It brought the entire ticketing system to something of a standstill.  
> 
> My question to you guys is how do I avoid something like this moving forward in the future?

I hit the same problem a few months ago.  I came up with a patch which helps with one slightly inefficient part of the code.  Jesse has already taken the patch into 3.9/4.0, but it isn't in 3.8.x.  The mailing list post which details the patch is here:

http://lists.bestpractical.com/pipermail/rt-users/2010-September/066454.html

You should find it helps a lot with these large tickets.  I had some tickets with more than 2000 transactions which were impossible to view before this patch was put in place.

Tim

-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE.