[rt-users] Merged Ticket Performance Degredation

[Mark Blackman]

You just need to upgrade your Sys::Syslog version.

should be fine after that.

- Mark

On 17 Oct 2008, at 19:57, Damon Miller wrote:

> Mark,
>
> Thanks very much for your quick reply.  I updated our config file as
> suggested but either the 'native' socket type isn't supported in Perl
> 5.8.5 on Linux or I'm doing something wrong.  Here's what happened  
> when
> I started the FastCGI handler from the command-line:
>
> Invalid argument passed to setlogsock; must be 'stream', 'unix',  
> 'tcp',
> 'udp' or 'inet' at /usr/lib/perl5/site_perl/5.8.5/Log/Dispatch/ 
> Syslog.pm
> line 66
>
> To make sure I followed your suggestion correctly, here are the last  
> few
> entries in our RT_SiteConfig.pm:
>
> --
>
> Set($AutoCreateNonExternalUsers,    1);
> Set($LogToFileNamed , "rt.log");
> Set($LogToFile , 'warning');
> Set($UseFriendlyFromLine , 0);
>
> @LogToSyslogConf = ( socket => 'native' ) unless (@LogToSyslogConf);
>
> 1;
>
> --
>
> As another potentially-relevant point, I also tried decreasing the
> verbosity of the logfile so as to eliminate the "We found a merged
> ticket" messages entirely.  Does that make the syslog update to
> RT_SiteConfig.pm unnecessary?  Even after reducing verbosity, I'm  
> still
> seeing the "hang" issue upon trying to load a merged ticket through  
> the
> UI.  Regardless, I just wanted to make sure I wasn't missing something
> between those two changes.
>
> Thanks again,
>
> Damon
>
>
> __
>
> Damon T. Miller
> Director of Application Services
> Thinking Phone Networks
> damon at thinkingphones.com
> 617-649-1388 (Office)
>
>
>> -----Original Message-----
>> From: Mark Blackman [mailto:mark at exonetric.com]
>> Sent: Friday, October 17, 2008 11:58 AM
>> To: Damon Miller
>> Cc: rt-users at lists.bestpractical.com
>> Subject: Re: [rt-users] Merged Ticket Performance Degredation
>>
>>
>> On 17 Oct 2008, at 16:39, Damon Miller wrote:
>>
>>> Hi all,
>>>
>>> We're experiencing an issue with RT 3.6.1 wherein loading merged
>>> tickets
>>> results in severe performance degredation, e.g. 100 - 300 seconds
> per
>>> ticket.  After 30 seconds, Apache gives up on the FastCGI script and
>>> generates a 500.  This problem has been documented and referenced in
>>> several posts, but I have been unable to find a resolution.
>>>
>>> Thanks for any suggestions or feedback.
>>
>> adding
>>
>> @LogToSyslogConf = ( socket => 'native' ) unless (@LogToSyslogConf);
>>
>> to RT_SiteConfig.pm sped up the merged ticket display from 260  
>> seconds
>> to about 6 seconds for us.
>>
>> probably still too many log messages being written for the reason
>> above I suppose.
>>
>> - Mark