CPRT (Client Perceived Response Time)

[Bidyadhar Patra]

Hai,
Could any body help me out in finding out the Client Perceived Response
Time for an ASP.Net application.

CPRT is measuring the time it takes for a page to load from browser click to
browser click. This takes into account network latency incurred by routing,
firewalls and proxies.

[Juan T. Llibre]

A simple way to find out the ASP.NET server
portion of the response time is to turn tracing on,
and view the trace results.

<%@ Page Trace="true" %>

For network profiling ( routing, firewalls and proxies ),
you'll need something else.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
=====================

"Bidyadhar Patra" <Bidyadhar Pa***@discussions.microsoft.com> wrote in
message news:76**********************************@microsof t.com...

Hai,
Could any body help me out in finding out the Client Perceived
Response
Time for an ASP.Net application.

CPRT is measuring the time it takes for a page to load from browser click
to
browser click. This takes into account network latency incurred by
routing,
firewalls and proxies.

[Bidyadhar Patra]

Thanks for the response.
Trace only gives the Request time not the Response time.

"Juan T. Llibre" wrote:

A simple way to find out the ASP.NET server
portion of the response time is to turn tracing on,
and view the trace results.

<%@ Page Trace="true" %>

For network profiling ( routing, firewalls and proxies ),
you'll need something else.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
=====================

"Bidyadhar Patra" <Bidyadhar Pa***@discussions.microsoft.com> wrote in
message news:76**********************************@microsof t.com...

Hai,
Could any body help me out in finding out the Client Perceived
Response
Time for an ASP.Net application.

CPRT is measuring the time it takes for a page to load from browser click
to
browser click. This takes into account network latency incurred by
routing,
firewalls and proxies.

[Juan T. Llibre]

Huh ?

Tracing acts as the result of a request,
but tracks the Response times !

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
=====================

"Bidyadhar Patra" <Bi************@discussions.microsoft.com> wrote in
message news:2E**********************************@microsof t.com...

Thanks for the response.
Trace only gives the Request time not the Response time. "Juan T. Llibre" wrote:

A simple way to find out the ASP.NET server
portion of the response time is to turn tracing on,
and view the trace results.

<%@ Page Trace="true" %>

For network profiling ( routing, firewalls and proxies ),
you'll need something else.

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
===================== "Bidyadhar Patra" <Bidyadhar Pa***@discussions.microsoft.com> wrote in
message news:76**********************************@microsof t.com...

> Hai,
> Could any body help me out in finding out the Client Perceived
> Response
> Time for an ASP.Net application.
>
> CPRT is measuring the time it takes for a page to load from browser
> click
> to
> browser click. This takes into account network latency incurred by
> routing,
> firewalls and proxies.