Re: Statistics
Re: Statistics
- Subject: Re: Statistics
- From: Kieran Kelleher <email@hidden>
- Date: Fri, 23 Apr 2010 23:14:55 -0400
This tells you what thread took the long time and it gives you a snapshot of what every thread was doing *HALF-WAY* thru the long time. In other words if your log.ERROR is set for 30 seconds then the log.WARN message shows what all threads were doing at 15 seconds into the request ...... thus giving you a fair idea what was going on in the entire app instance.
On Apr 23, 2010, at 2:35 PM, Ricardo J. Parada wrote:
> Quick question on this stuff... :-)
>
> When a request is taking long, this just logs the stack traces of the different threads in the application? Is that what this gives you?
>
> Thanks,
> Ricardo
>
>
>
> On Apr 23, 2010, at 1:38 PM, Kieran Kelleher wrote:
>
>> Wonder of course, what else could you look at?!
>>
>> - ERXStatistics
>>
>>
>>
>> ERXStatisticsStore request timer logging
>> er.extensions.ERXStatisticsStore.milliSeconds.warn=3000
>> er.extensions.ERXStatisticsStore.milliSeconds.error=15000
>> er.extensions.ERXStatisticsStore.milliSeconds.fatal=30000
>>
>>
>>
>> and call this in your app constructor
>>
>> setStatisticsStore(new ERXStatisticsStore());
>>
>>
>> On Apr 23, 2010, at 12:49 PM, Ricardo J. Parada wrote:
>>
>>> Hi,
>>>
>>> What should I look at to find out the time a request sits in the queue before it is picked up and processed?
>>>
>>> Thanks,
>>> Ricardo
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden