You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Matteo Caprari <ma...@gmail.com> on 2010/01/05 13:11:04 UTC
in _stats, how is couchdb.request_time calculated?
Hi.
I'm looking at this snippet from _stats?range=60
"couchdb": {
"request_time": {
"description": "",
"current": 36.5,
"sum": 36.5,
"mean": 18.25,
"stddev": 22.274,
"min": 2.5,
"max": 34.0
},
Looking at how numbers add up, it looks like there have been 2
requests, but 'sum' is 3 in http.requests for the same period
"requests": {
"description": "number of HTTP requests",
"current": 3.0,
"sum": 3.0,
"mean": 0.05,
"stddev": 0.287,
"min": 0,
"max": 2
}
tnx
--
:Matteo Caprari
matteo.caprari@gmail.com
Re: in _stats, how is couchdb.request_time calculated?
Posted by Paul Davis <pa...@gmail.com>.
Looks right to me.
On Thu, Jan 7, 2010 at 1:47 PM, Matteo Caprari <ma...@gmail.com> wrote:
> Oh well well if you want somethig to do...
>
> Do you think this view is the right way to correctly generate response
> time reports?
>
> http://github.com/mcaprari/couchdb-stats/tree/master/app/views/request_time/
> (despite the fancy name, the key is just date split in its components)
>
> Don't tell me, today I was about to be crushed by a double decker :)
>
> On Thu, Jan 7, 2010 at 1:31 PM, Paul Davis <pa...@gmail.com> wrote:
>> Oh, I see what you're saying. I'll have to dig into it this weekend
>> when I get home. You're actually giving me something worth thinking
>> about as I just trawl through email occasionally to burn time.
>> Internet cafes are a brief respite from trying to walk on the ice
>> rinks that are Britain's sidewalks.
>>
>> Paul Davis
>>
>> On Tue, Jan 5, 2010 at 5:39 PM, Matteo Caprari <ma...@gmail.com> wrote:
>>> Thanks paul :)
>>>
>>> I swear, I'm not trying to disturb your holiday. But I still don't
>>> understand why couchdb.requests_time sees 2 requests while
>>> httpd.requests sees 3 (it this is what is happening).
>>>
>>> My ass is freezing, hope your holidays are warm :)
>>>
>>> On Tue, Jan 5, 2010 at 4:56 PM, Paul Davis <pa...@gmail.com> wrote:
>>>> Still just shooting from memory on holiday, but that should mean that
>>>> you only had 2 requests in a 1 second window of the 60 seconds. The
>>>> stats modules work by accumulating values and then aggregating. The
>>>> different range query parameters just show a longer history for each
>>>> endpoint.
>>>>
>>>> HTH,
>>>> Paul Davis
>>>>
>>>> On Tue, Jan 5, 2010 at 12:11 PM, Matteo Caprari
>>>> <ma...@gmail.com> wrote:
>>>>> Hi.
>>>>>
>>>>> I'm looking at this snippet from _stats?range=60
>>>>>
>>>>> "couchdb": {
>>>>> "request_time": {
>>>>> "description": "",
>>>>> "current": 36.5,
>>>>> "sum": 36.5,
>>>>> "mean": 18.25,
>>>>> "stddev": 22.274,
>>>>> "min": 2.5,
>>>>> "max": 34.0
>>>>> },
>>>>>
>>>>> Looking at how numbers add up, it looks like there have been 2
>>>>> requests, but 'sum' is 3 in http.requests for the same period
>>>>>
>>>>> "requests": {
>>>>> "description": "number of HTTP requests",
>>>>> "current": 3.0,
>>>>> "sum": 3.0,
>>>>> "mean": 0.05,
>>>>> "stddev": 0.287,
>>>>> "min": 0,
>>>>> "max": 2
>>>>> }
>>>>>
>>>>> tnx
>>>>>
>>>>> --
>>>>> :Matteo Caprari
>>>>> matteo.caprari@gmail.com
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> :Matteo Caprari
>>> matteo.caprari@gmail.com
>>>
>>
>
>
>
> --
> :Matteo Caprari
> matteo.caprari@gmail.com
>
Re: in _stats, how is couchdb.request_time calculated?
Posted by Matteo Caprari <ma...@gmail.com>.
Oh well well if you want somethig to do...
Do you think this view is the right way to correctly generate response
time reports?
http://github.com/mcaprari/couchdb-stats/tree/master/app/views/request_time/
(despite the fancy name, the key is just date split in its components)
Don't tell me, today I was about to be crushed by a double decker :)
On Thu, Jan 7, 2010 at 1:31 PM, Paul Davis <pa...@gmail.com> wrote:
> Oh, I see what you're saying. I'll have to dig into it this weekend
> when I get home. You're actually giving me something worth thinking
> about as I just trawl through email occasionally to burn time.
> Internet cafes are a brief respite from trying to walk on the ice
> rinks that are Britain's sidewalks.
>
> Paul Davis
>
> On Tue, Jan 5, 2010 at 5:39 PM, Matteo Caprari <ma...@gmail.com> wrote:
>> Thanks paul :)
>>
>> I swear, I'm not trying to disturb your holiday. But I still don't
>> understand why couchdb.requests_time sees 2 requests while
>> httpd.requests sees 3 (it this is what is happening).
>>
>> My ass is freezing, hope your holidays are warm :)
>>
>> On Tue, Jan 5, 2010 at 4:56 PM, Paul Davis <pa...@gmail.com> wrote:
>>> Still just shooting from memory on holiday, but that should mean that
>>> you only had 2 requests in a 1 second window of the 60 seconds. The
>>> stats modules work by accumulating values and then aggregating. The
>>> different range query parameters just show a longer history for each
>>> endpoint.
>>>
>>> HTH,
>>> Paul Davis
>>>
>>> On Tue, Jan 5, 2010 at 12:11 PM, Matteo Caprari
>>> <ma...@gmail.com> wrote:
>>>> Hi.
>>>>
>>>> I'm looking at this snippet from _stats?range=60
>>>>
>>>> "couchdb": {
>>>> "request_time": {
>>>> "description": "",
>>>> "current": 36.5,
>>>> "sum": 36.5,
>>>> "mean": 18.25,
>>>> "stddev": 22.274,
>>>> "min": 2.5,
>>>> "max": 34.0
>>>> },
>>>>
>>>> Looking at how numbers add up, it looks like there have been 2
>>>> requests, but 'sum' is 3 in http.requests for the same period
>>>>
>>>> "requests": {
>>>> "description": "number of HTTP requests",
>>>> "current": 3.0,
>>>> "sum": 3.0,
>>>> "mean": 0.05,
>>>> "stddev": 0.287,
>>>> "min": 0,
>>>> "max": 2
>>>> }
>>>>
>>>> tnx
>>>>
>>>> --
>>>> :Matteo Caprari
>>>> matteo.caprari@gmail.com
>>>>
>>>
>>
>>
>>
>> --
>> :Matteo Caprari
>> matteo.caprari@gmail.com
>>
>
--
:Matteo Caprari
matteo.caprari@gmail.com
Re: in _stats, how is couchdb.request_time calculated?
Posted by Paul Davis <pa...@gmail.com>.
Oh, I see what you're saying. I'll have to dig into it this weekend
when I get home. You're actually giving me something worth thinking
about as I just trawl through email occasionally to burn time.
Internet cafes are a brief respite from trying to walk on the ice
rinks that are Britain's sidewalks.
Paul Davis
On Tue, Jan 5, 2010 at 5:39 PM, Matteo Caprari <ma...@gmail.com> wrote:
> Thanks paul :)
>
> I swear, I'm not trying to disturb your holiday. But I still don't
> understand why couchdb.requests_time sees 2 requests while
> httpd.requests sees 3 (it this is what is happening).
>
> My ass is freezing, hope your holidays are warm :)
>
> On Tue, Jan 5, 2010 at 4:56 PM, Paul Davis <pa...@gmail.com> wrote:
>> Still just shooting from memory on holiday, but that should mean that
>> you only had 2 requests in a 1 second window of the 60 seconds. The
>> stats modules work by accumulating values and then aggregating. The
>> different range query parameters just show a longer history for each
>> endpoint.
>>
>> HTH,
>> Paul Davis
>>
>> On Tue, Jan 5, 2010 at 12:11 PM, Matteo Caprari
>> <ma...@gmail.com> wrote:
>>> Hi.
>>>
>>> I'm looking at this snippet from _stats?range=60
>>>
>>> "couchdb": {
>>> "request_time": {
>>> "description": "",
>>> "current": 36.5,
>>> "sum": 36.5,
>>> "mean": 18.25,
>>> "stddev": 22.274,
>>> "min": 2.5,
>>> "max": 34.0
>>> },
>>>
>>> Looking at how numbers add up, it looks like there have been 2
>>> requests, but 'sum' is 3 in http.requests for the same period
>>>
>>> "requests": {
>>> "description": "number of HTTP requests",
>>> "current": 3.0,
>>> "sum": 3.0,
>>> "mean": 0.05,
>>> "stddev": 0.287,
>>> "min": 0,
>>> "max": 2
>>> }
>>>
>>> tnx
>>>
>>> --
>>> :Matteo Caprari
>>> matteo.caprari@gmail.com
>>>
>>
>
>
>
> --
> :Matteo Caprari
> matteo.caprari@gmail.com
>
Re: in _stats, how is couchdb.request_time calculated?
Posted by Matteo Caprari <ma...@gmail.com>.
Thanks paul :)
I swear, I'm not trying to disturb your holiday. But I still don't
understand why couchdb.requests_time sees 2 requests while
httpd.requests sees 3 (it this is what is happening).
My ass is freezing, hope your holidays are warm :)
On Tue, Jan 5, 2010 at 4:56 PM, Paul Davis <pa...@gmail.com> wrote:
> Still just shooting from memory on holiday, but that should mean that
> you only had 2 requests in a 1 second window of the 60 seconds. The
> stats modules work by accumulating values and then aggregating. The
> different range query parameters just show a longer history for each
> endpoint.
>
> HTH,
> Paul Davis
>
> On Tue, Jan 5, 2010 at 12:11 PM, Matteo Caprari
> <ma...@gmail.com> wrote:
>> Hi.
>>
>> I'm looking at this snippet from _stats?range=60
>>
>> "couchdb": {
>> "request_time": {
>> "description": "",
>> "current": 36.5,
>> "sum": 36.5,
>> "mean": 18.25,
>> "stddev": 22.274,
>> "min": 2.5,
>> "max": 34.0
>> },
>>
>> Looking at how numbers add up, it looks like there have been 2
>> requests, but 'sum' is 3 in http.requests for the same period
>>
>> "requests": {
>> "description": "number of HTTP requests",
>> "current": 3.0,
>> "sum": 3.0,
>> "mean": 0.05,
>> "stddev": 0.287,
>> "min": 0,
>> "max": 2
>> }
>>
>> tnx
>>
>> --
>> :Matteo Caprari
>> matteo.caprari@gmail.com
>>
>
--
:Matteo Caprari
matteo.caprari@gmail.com
Re: in _stats, how is couchdb.request_time calculated?
Posted by Paul Davis <pa...@gmail.com>.
Still just shooting from memory on holiday, but that should mean that
you only had 2 requests in a 1 second window of the 60 seconds. The
stats modules work by accumulating values and then aggregating. The
different range query parameters just show a longer history for each
endpoint.
HTH,
Paul Davis
On Tue, Jan 5, 2010 at 12:11 PM, Matteo Caprari
<ma...@gmail.com> wrote:
> Hi.
>
> I'm looking at this snippet from _stats?range=60
>
> "couchdb": {
> "request_time": {
> "description": "",
> "current": 36.5,
> "sum": 36.5,
> "mean": 18.25,
> "stddev": 22.274,
> "min": 2.5,
> "max": 34.0
> },
>
> Looking at how numbers add up, it looks like there have been 2
> requests, but 'sum' is 3 in http.requests for the same period
>
> "requests": {
> "description": "number of HTTP requests",
> "current": 3.0,
> "sum": 3.0,
> "mean": 0.05,
> "stddev": 0.287,
> "min": 0,
> "max": 2
> }
>
> tnx
>
> --
> :Matteo Caprari
> matteo.caprari@gmail.com
>