Hehe thanks Charles.

I think you might have a point anyway. Running that script recommended by Jason 
has thrown up a few things that need tweaking with mysql.

Not sure what some of them mean yet, and not sure if it'll help, but we'll see.

I appreciate you helping believe me!

Justin

-------------------------------------------------
Justin Hayes
OpenBet Support Manager
justin.ha...@openbet.com

On 29 Jun 2010, at 15:28, Charles Johnson wrote:

> Justin, thank you for the kindness of your reply. I didn't intend to send you 
> chasing rabbits, so to speak. Just offering something to add to the checklist 
> of items to be crossed off before digging too deeply into the perl code. If 
> you are convinced that mysql is performing at its best then please ignore my 
> noise! :)
> 
> Cheers--
> 
> Charles
> On Jun 29, 2010, at 9:18 AM, Justin Hayes wrote:
> 
>> Hi Charles,
>> 
>> But as far as we can tell from our profiling the time is spent in the perl 
>> rendering the ticket, not in the query used to retrieve the ticket and 
>> attachments in the first place (which happens once at the start I believe). 
>> The loop that renders the ticket history and each attachment takes anything 
>> up to 20+ seconds.
>> 
>> So I'm not sure how the DB can be an issue here? Unless I'm wrong about it 
>> doing 1 big query at the start and there are loads of little queries inside 
>> the loop.
>> 
>> Cheers,
>> 
>> Justin
>> 
>> -------------------------------------------------
>> Justin Hayes
>> OpenBet Support Manager
>> justin.ha...@openbet.com
>> 
>> On 29 Jun 2010, at 15:14, Charles Johnson wrote:
>> 
>>> Quite outside of the speed of RT, what database are you using as a 
>>> back-end? How long has it been since you did some care and feeding of your 
>>> database? How big are your tables? If you are using mysql or postgres have 
>>> you used their tools to examine your database, especially the indexes and 
>>> statistics? This may be an issue with indexes needing to be rebuilt, or 
>>> asking the database to gather new statistics for the queries your are 
>>> running.
>>> 
>>> Cheers--
>>> 
>>> Charles
>>> 
>>> On Jun 29, 2010, at 8:09 AM, 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
>>> 
>>> --
>>> Charles Johnson, Vanderbilt University
>>> Advanced Computing Center for Research & Education
>>> Mailing Address:  Peabody #34, 230 Appleton Place, Nashville, TN 37203
>>> Shipping Address: 1231 18th Avenue South, Hill Center, Suite 143, 
>>> Nashville, TN 37212
>>> Office: 615-343-4134
>>> Cell: 615-478-5743
>>> Fax: 615-343-7216
>>> charles.john...@accre.vanderbilt.edu
>>> 
>> 
> 
> --
> Charles Johnson, Vanderbilt University
> Advanced Computing Center for Research & Education
> Mailing Address:  Peabody #34, 230 Appleton Place, Nashville, TN 37203
> Shipping Address: 1231 18th Avenue South, Hill Center, Suite 143, Nashville, 
> TN 37212
> Office: 615-343-4134
> Cell: 615-478-5743
> Fax: 615-343-7216


Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Reply via email to