[rt-users] RT Query Logging

[Raed El-Hames]

There is no bother, what I meant is the list will be more helpful than me.
for tweaks and performance tuning the wiki and mailing list is better 
place than me, because it varies depending on the database server you use.
Start with observation and detect your bottle necks , ist the web part 
or the database, in most cases the later, which part of the application 
is slow, creating tickets or searching tickets etc etc

Regards

Roy

Varun Vyas wrote:
> Hi Raed El-Hames
>
> I am so sorry if i have bothered you but as i am new to this mail list i 
> am also not aware that i need to reply to all users in list and not 
> individual.
>
>
> Raed El-Hames wrote:
>   
>> Varun;
>>
>> You should make it a habit to reply to the list and not individuals , 
>> I have never deployed RT with Oracle so can't help you --
>> few in the may though
>>
>>
>> ps: A pointer so you know what RT is capable of , our RT db is > 50G 
>> in size, the attachments table alone is > 26G, our db server is quad 
>> dual core with 16 G Ram (4x4) and the web server is standard 3.6G cpu 
>> with 3G Ram, average per day tickets is ~ 1000 with 200 internal users 
>> and 10000+ external customer users.
>>
>> Regards;
>> Roy
>>
>>
>>
>>
>>
>> Varun Vyas wrote:
>>     
>>> We have deployed RT 3.6.3 on oracle 9i database as an backend
>>> in a medium sized firm and we have lots of tickets processed
>>> everyday more than 100. My problem is that the application is very
>>> irresponsive and very slow. We have already 8 gigs of RAM on our
>>> webserver with Apache 2.0 and fastCGI implemented. Also we have
>>> performed indexing on our oracle database with fastcgi implemented. 
>>> But nothing seems to be going in our way. So please anyone can 
>>> suggest wat will be the problem. I m looking for concerete answer to 
>>> my problem. On which side i need to tune on application side or on 
>>> database side and if on both side what step i need to take to make my 
>>> application lightning fast.With acceptable level of performance.
>>>
>>> And i have looked for all this things in google and have searched a 
>>> lot from past two months but has found nothing.
>>>
>>>
>>>
>>> Raed El-Hames wrote:
>>>  
>>>       
>>>> Varun;
>>>>
>>>> There is no straight forward answer to this , you possibly should 
>>>> start by stating your RT version, DB type(oracle,mysql ??) and 
>>>> version , apache, mod_perl or fastcgi  etc ..
>>>> Also search the wiki and mailing list there are lots of posts and a 
>>>> good article in the wiki covering this.(sorry don't remember the url).
>>>>
>>>> Good luck;
>>>>
>>>> Roy
>>>>
>>>>
>>>> Varun Vyas wrote:
>>>>    
>>>>         
>>>>> And i want to know one more thing as my RT is slow right now .What 
>>>>> steps should i take to increase its performance on application side 
>>>>> or on database side. We have remote database on our RT and it has 2 
>>>>> gigs RAM.
>>>>>
>>>>> Raed El-Hames wrote:
>>>>>  
>>>>>      
>>>>>           
>>>>>> From RT_Config.pm
>>>>>>
>>>>>> # DBIx-SearchBuilder 1.31_1 or higher; simply set $StatementLog to be
>>>>>> # the level that you wish SQL statements to be logged at.
>>>>>> Set($StatementLog,undef);
>>>>>>
>>>>>> I am not sure what the different levels but :
>>>>>> Set($StatementLog,1);
>>>>>>
>>>>>> will be a good start.
>>>>>> Remember to restart your web server.
>>>>>>
>>>>>> Regards;
>>>>>>
>>>>>> Roy
>>>>>>
>>>>>>
>>>>>> Varun Vyas wrote:
>>>>>>           
>>>>>>             
>>>>>>> Hello All
>>>>>>>
>>>>>>> Can anyone can tell me how i can log my queries that hits my 
>>>>>>> database in RT.log. I am using oracle 9i and RT 3.6.3 we have a 
>>>>>>> performance issue as our RT is very slow and takes 15-20 seconds 
>>>>>>> for database operations. So i want to log my queries so that i 
>>>>>>> can then analyze them for performance optimisation. And also i m 
>>>>>>> getting internal server error frequently can any one tell me how 
>>>>>>> can i correct it
>>>>>>>
>>>>>>> Any help in highly appreciated
>>>>>>>
>>>>>>>                   
>>>>>>>               
>>>>>>             
>>>>>>             
>>>>>         
>>>>>           
>>>>     
>>>>         
>>>   
>>>       
>>     
>
>
>