Hi All,

I'm working on a project that involves migration of a browser-based application from VB-ASP to ASP.NET. 

While on a 10 MBps LAN, the migrated application is faster and more scalable compared to the old one, the response times for the
ASP.NET pages shoot up when requests are made across a WAN. The WAN is made up of 2 LANs, connected by a 2 MBps dedicated link that
uses Frame Relay .

On an average, the new ASP.NET pages are about 20% larger compared to pages of the old application (HTML file size wise) but the
average response time is at least 150% more.

I'll be grateful if someone could hint on possible reasons behind this discrimination of a WAN against ASP.NET.

Thanks in advance.

Dipak Jha

Dipak,

I can't see that this would cause any problems, ASP.NET pages should run
with network speed issues,

ASP.NET pages run with no speed problem across my 56k modem connection to
the internet or RAS.

HTML is very small anyway and a 20% increase in size should unnoticeable
across a 2mb link.

Have you checked all your images ??

Daniel




----- Original Message -----
From: "Dipak Jha" <dipak.jha@p...>
To: "ASP.NET" <aspx@p...>
Cc: <dipak.jha@p...>
Sent: Tuesday, March 11, 2003 7:32 AM
Subject: [aspx] Performance degradation across a WAN: Please help


> Hi All,
>
> I'm working on a project that involves migration of a browser-based
application from VB-ASP to ASP.NET.
>
> While on a 10 MBps LAN, the migrated application is faster and more
scalable compared to the old one, the response times for the ASP.NET pages
shoot up when requests are made across a WAN. The WAN is made up of 2 LANs,
connected by a 2 MBps dedicated link that uses Frame Relay .
>
> On an average, the new ASP.NET pages are about 20% larger compared to
pages of the old application (HTML file size wise) but the average response
time is at least 150% more.
>
> I'll be grateful if someone could hint on possible reasons behind this
discrimination of a WAN against ASP.NET.
>
> Thanks in advance.
>
> Dipak Jha
>
>
>

Sorry, I did mean without network speed issues

----- Original Message -----
From: "Daniel Klemm" <daniel_klemm@b...>
To: "ASP.NET" <aspx@p...>
Sent: Tuesday, March 11, 2003 9:44 AM
Subject: [aspx] Re: Performance degradation across a WAN: Please help


> Dipak,
>
> I can't see that this would cause any problems, ASP.NET pages should run
> with network speed issues,
>
> ASP.NET pages run with no speed problem across my 56k modem connection to
> the internet or RAS.
>
> HTML is very small anyway and a 20% increase in size should unnoticeable
> across a 2mb link.
>
> Have you checked all your images ??
>
> Daniel
>
>
>
>
> ----- Original Message -----
> From: "Dipak Jha" <dipak.jha@p...>
> To: "ASP.NET" <aspx@p...>
> Cc: <dipak.jha@p...>
> Sent: Tuesday, March 11, 2003 7:32 AM
> Subject: [aspx] Performance degradation across a WAN: Please help
>
>
> > Hi All,
> >
> > I'm working on a project that involves migration of a browser-based
> application from VB-ASP to ASP.NET.
> >
> > While on a 10 MBps LAN, the migrated application is faster and more
> scalable compared to the old one, the response times for the ASP.NET pages
> shoot up when requests are made across a WAN. The WAN is made up of 2
LANs,
> connected by a 2 MBps dedicated link that uses Frame Relay .
> >
> > On an average, the new ASP.NET pages are about 20% larger compared to
> pages of the old application (HTML file size wise) but the average
response
> time is at least 150% more.
> >
> > I'll be grateful if someone could hint on possible reasons behind this
> discrimination of a WAN against ASP.NET.
> >
> > Thanks in advance.
> >
> > Dipak Jha
> >
> >
> >
>
>
>

Hi Dipak,

Bear in mind that all server-side web controls maintain viewstate in the
page unless they have been explicitly insructed not to. This can be done
either at web-control level or at page level.

Make sure that pages that display large tables of information, or pages with
many controls that do not require postback have been set to EnableViewState
= False.

View the source of your pages to check the size of the viewstate, and
determine if viewstate is neccessary on the page/control or not.

Greg

----- Original Message -----
From: "Dipak Jha" <dipak.jha@p...>
To: "ASP.NET" <aspx@p...>
Cc: <dipak.jha@p...>
Sent: Tuesday, March 11, 2003 9:32 AM
Subject: [aspx] Performance degradation across a WAN: Please help


> Hi All,
>
> I'm working on a project that involves migration of a browser-based
application from VB-ASP to ASP.NET.
>
> While on a 10 MBps LAN, the migrated application is faster and more
scalable compared to the old one, the response times for the ASP.NET pages
shoot up when requests are made across a WAN. The WAN is made up of 2 LANs,
connected by a 2 MBps dedicated link that uses Frame Relay .
>
> On an average, the new ASP.NET pages are about 20% larger compared to
pages of the old application (HTML file size wise) but the average response
time is at least 150% more.
>
> I'll be grateful if someone could hint on possible reasons behind this
discrimination of a WAN against ASP.NET.
>
> Thanks in advance.
>
> Dipak Jha
>
>

Thanks Greg.

But I guess turning off of the viewstate would only lead to some cutting
down in terms of the html that is streamed out to the client. Would that be
significant on a link that is as broad as 2Mbps?

Anyway, I'll try this out and let you know.

Regards,

Dipak Jha

----- Original Message -----
From: "Greg Quinn" <greg@i...>
To: "ASP.NET" <aspx@p...>
Sent: Tuesday, March 11, 2003 3:40 PM
Subject: [aspx] Re: Performance degradation across a WAN: Please help


> Hi Dipak,
>
> Bear in mind that all server-side web controls maintain viewstate in the
> page unless they have been explicitly insructed not to. This can be done
> either at web-control level or at page level.
>
> Make sure that pages that display large tables of information, or pages
with
> many controls that do not require postback have been set to
EnableViewState
> = False.
>
> View the source of your pages to check the size of the viewstate, and
> determine if viewstate is neccessary on the page/control or not.
>
> Greg
>
> ----- Original Message -----
> From: "Dipak Jha" <dipak.jha@p...>
> To: "ASP.NET" <aspx@p...>
> Cc: <dipak.jha@p...>
> Sent: Tuesday, March 11, 2003 9:32 AM
> Subject: [aspx] Performance degradation across a WAN: Please help
>
>
> > Hi All,
> >
> > I'm working on a project that involves migration of a browser-based
> application from VB-ASP to ASP.NET.
> >
> > While on a 10 MBps LAN, the migrated application is faster and more
> scalable compared to the old one, the response times for the ASP.NET pages
> shoot up when requests are made across a WAN. The WAN is made up of 2
LANs,
> connected by a 2 MBps dedicated link that uses Frame Relay .
> >
> > On an average, the new ASP.NET pages are about 20% larger compared to
> pages of the old application (HTML file size wise) but the average
response
> time is at least 150% more.
> >
> > I'll be grateful if someone could hint on possible reasons behind this
> discrimination of a WAN against ASP.NET.
> >
> > Thanks in advance.
> >
> > Dipak Jha
> >
> >
>
>

If the site is not really very busy, no it wont make much of a difference.

I would also suggest you browse through some asp.net performance articles,
there may be a few reasons your pages are not taking advantage of the speed
.net has to offer, which is causing the 150% increase in response time

Greg

----- Original Message -----
From: "Dipak Jha" <dipak.jha@p...>
To: "ASP.NET" <aspx@p...>
Sent: Tuesday, March 11, 2003 1:17 PM
Subject: [aspx] Re: Performance degradation across a WAN: Please help


> Thanks Greg.
>
> But I guess turning off of the viewstate would only lead to some cutting
> down in terms of the html that is streamed out to the client. Would that
be
> significant on a link that is as broad as 2Mbps?
>
> Anyway, I'll try this out and let you know.
>
> Regards,
>
> Dipak Jha
>
> ----- Original Message -----
> From: "Greg Quinn" <greg@i...>
> To: "ASP.NET" <aspx@p...>
> Sent: Tuesday, March 11, 2003 3:40 PM
> Subject: [aspx] Re: Performance degradation across a WAN: Please help
>
>
> > Hi Dipak,
> >
> > Bear in mind that all server-side web controls maintain viewstate in the
> > page unless they have been explicitly insructed not to. This can be done
> > either at web-control level or at page level.
> >
> > Make sure that pages that display large tables of information, or pages
> with
> > many controls that do not require postback have been set to
> EnableViewState
> > = False.
> >
> > View the source of your pages to check the size of the viewstate, and
> > determine if viewstate is neccessary on the page/control or not.
> >
> > Greg
> >
> > ----- Original Message -----
> > From: "Dipak Jha" <dipak.jha@p...>
> > To: "ASP.NET" <aspx@p...>
> > Cc: <dipak.jha@p...>
> > Sent: Tuesday, March 11, 2003 9:32 AM
> > Subject: [aspx] Performance degradation across a WAN: Please help
> >
> >
> > > Hi All,
> > >
> > > I'm working on a project that involves migration of a browser-based
> > application from VB-ASP to ASP.NET.
> > >
> > > While on a 10 MBps LAN, the migrated application is faster and more
> > scalable compared to the old one, the response times for the ASP.NET
pages
> > shoot up when requests are made across a WAN. The WAN is made up of 2
> LANs,
> > connected by a 2 MBps dedicated link that uses Frame Relay .
> > >
> > > On an average, the new ASP.NET pages are about 20% larger compared to
> > pages of the old application (HTML file size wise) but the average
> response
> > time is at least 150% more.
> > >
> > > I'll be grateful if someone could hint on possible reasons behind this
> > discrimination of a WAN against ASP.NET.
> > >
> > > Thanks in advance.
> > >
> > > Dipak Jha
> > >
> > >
> >
> >
>
>

Hi All,

This is in reference to the problem I described to the group earlier.

My preliminary investigations using a packet-capture tool called "Ethereal", that allows the user to set source and destination IP
addresses as filters, indicate that:

For a specific request:

With the new ASP.NET application, 50 packets are sent by the client to the web server and 70 packets are sent by the web server to
the client. The total is 120.

With the legacy (VB-ASP) application, 36 packets are sent by the client to the webserver and 60 packets are sent by the web server
to the client. The total is 96.



The web pages returned by the server in the two cases are identical.

Thus in terms of number of packets exchanged between the client and the server, ASP.NET is more voluminous by a factor of 120 / 96 
i.e  1.25 compared to VB-ASP.

This definitely is one of the prime reasons behind degradation of performance of  my ASP.NET application across a WAN where packet
exchange starts mattering (in contrast to a LAN). 

Why does ASP.NET transact more in terms of packets? Is it because of overheads associated with a more elaborate client-server
handshake associated with each request? Or are there some security features that CLR has to settle before it can service such
requests?

I request the group to provide clues / hints.


Regards,

Dipak Jha

----- Original Message ----- 
From: "Dipak Jha" <dipak.jha@p...>
To: "ASP.NET" <aspx@p...>
Cc: <dipak.jha@p...>
Sent: Tuesday, March 11, 2003 1:02 PM
Subject: [aspx] Performance degradation across a WAN: Please help


> Hi All,
> 
> I'm working on a project that involves migration of a browser-based application from VB-ASP to ASP.NET. 
> 
> While on a 10 MBps LAN, the migrated application is faster and more scalable compared to the old one, the response times for
the ASP.NET pages shoot up when requests are made across a WAN. The WAN is made up of 2 LANs, connected by a 2 MBps dedicated link
that uses Frame Relay .
> 
> On an average, the new ASP.NET pages are about 20% larger compared to pages of the old application (HTML file size wise) but
the average response time is at least 150% more.
> 
> I'll be grateful if someone could hint on possible reasons behind this discrimination of a WAN against ASP.NET.
> 
> Thanks in advance.
> 
> Dipak Jha
> 
>