[rt-users] RT response time

[Raed El-Hames]

Thanks Matthew,
I use Firebug during the development but for my purposes I would need 
something robotic collecting and stating in the back ground, although 
some its suggestions/recommendations is not always useful.
I have considered/ing the web logs, and using 'rt_base_time', but both 
these are server responses (which logically should be all I need), 
however the powers above me (and to a certain extent have a good point), 
suggests that the server time is a fraction of the time it takes to 
display a page and I have tested on a DualCore 2.6 GH with 2G ram 
running windows xp no applications except using IE7 pulling an average 
ticket with 9 updates -no attachments and few ticket custom fields , the 
rt_base_time was ~ 1.5 seconds however it took around 8 seconds for the 
page to display .. This done few times at different time of the day, the 
link between my client and the rt server is Gig link ..

Does anyone else see this slowness?

Roy
 

Matthew Seaman wrote:
> Matthew Seaman wrote:
>> Raed El-Hames wrote:
>>
>>> Versions 3.6.4 and 3.8.5
>>> apache2,mod_perl2 and mysql5
>>>
>>> Have anyone done any kind of monitoring / profiling of RT response 
>>> time, ie measure the time it takes to display a ticket / (or create 
>>> a ticket but possibly doing this every 5/10 minutes wont be desirable)
>>> Can anyone recommend any software (preferably open source) that can 
>>> do that?
>>
>> If you modify the apache log format, you can get it to include the 
>> amount
>> of time it spends to serve each page.  Something like this:
>>
>> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" 
>> \"%{User-Agent}i\" %D"
>>
>> (See http://httpd.apache.org/docs/2.2/mod/mod_log_config.html)
>>
>> %D is the time in microseconds it takes to serve the request.  
>> There's also
>> %T, but that's measured in integer numbers of seconds, so it's almost 
>> always
>> 0 for any reasonably good web-server.  %D is to some extent 
>> determined by
>> how fast the web clients can receive the data, but this should not be 
>> rate limiting unless you have particularly old and slow client 
>> machines or people accessing the site through dial-up connections.
>>
>> AFAIK most weblog analysis software doesn't deal with the time taken 
>> to serve
>> a request, because that data isn't included in the standard log file 
>> formats.
>> However, writing a small perl script to calculate statistics for each 
>> of the different queries (%r in the format) should be fairly trivial 
>> to do.
>>
>
> Another approach is to use the Firebug extension to Firefox -- this
> gives you a detailed breakdown of the time it takes to display a web
> page (including all of the sub-requests for images etc.)
>
> http://getfirebug.com/
>
> Only shows you timings for one page at a time though, and needs to be
> run interactively.
>
>     Cheers,
>
>     Matthew
>