Hi,

I had written to the group earlier too on this but since I did not recieve
any response and since the problem continues to plague my project, I'm
narrating the story again.

I've migrated a legacy application, writen in VB-ASP to ASP.NET. The pages
and business logic are identical. On my local LAN, the ASP.NET application
is faster and more sclable. But on a WAN (2 LANs connected through a 2 Mbps
link across a 1000 Kilometers), the ASP.NET application is 1.5 - 2 times
slower. This led me to capture packets (using a packet capture tool called
"ethereal") and then count the number of packets transacted per HTTP
request. I found that though the ASP.NET produced pages are smaller (by a
factor of 0.75) compared to the legacy pages, the number of packets
transacted between the client and the web-server is 1.44 times higher
compared to the legacy application.

Why does ASP.NET transact more in terms of packets exchanged? Is there a way
to overcome this problem?

Please send in your views on this. I'm in a real fix and would appreciate
any help in this regard.

Regards,

Dipak Jha

did you measure the page size in terms of the html source pushed to the browser or just the design time
html of your aspx pages ?. To maintain view state of your controls Asp.net sends an encoded string stored in hidden variables; to
the browser which is then decoded by runtime, this might be the cause for the additional packets generated.

You have to use viewstate of controls selectively to avoid such overheads.

Regards,
Sakthi.



-----Original Message-----
From: Dipak Jha [mailto:dipak.jha@p...]
Sent: Friday, March 14, 2003 3:21 PM
To: ASP.NET
Subject: [aspx] High packet count


Hi,

I had written to the group earlier too on this but since I did not recieve
any response and since the problem continues to plague my project, I'm
narrating the story again.

I've migrated a legacy application, writen in VB-ASP to ASP.NET. The pages
and business logic are identical. On my local LAN, the ASP.NET application
is faster and more sclable. But on a WAN (2 LANs connected through a 2 Mbps
link across a 1000 Kilometers), the ASP.NET application is 1.5 - 2 times
slower. This led me to capture packets (using a packet capture tool called
"ethereal") and then count the number of packets transacted per HTTP
request. I found that though the ASP.NET produced pages are smaller (by a
factor of 0.75) compared to the legacy pages, the number of packets
transacted between the client and the web-server is 1.44 times higher
compared to the legacy application.

Why does ASP.NET transact more in terms of packets exchanged? Is there a way
to overcome this problem?

Please send in your views on this. I'm in a real fix and would appreciate
any help in this regard.

Regards,

Dipak Jha

Hi Sakthi,

The pagesize I'm talking about is the size of the actual html pushed to the
browser. And yes, within that html, I can see those encoded strings / view
state information etc that you have talked about.

Regards,

Dipak Jha

----- Original Message -----
From: "Palani, Sakthivel (Cognizant)" <PSakthiv@c...>
To: "ASP.NET" <aspx@p...>
Sent: Friday, March 14, 2003 3:31 PM
Subject: [aspx] RE: High packet count


> did you measure the page size in terms of the html source pushed to the
browser or just the design time html of your aspx pages ?. To maintain view
state of your controls Asp.net sends an encoded string stored in hidden
variables; to the browser which is then decoded by runtime, this might be
the cause for the additional packets generated.
>
> You have to use viewstate of controls selectively to avoid such overheads.
>
> Regards,
> Sakthi.
>
>
>
> -----Original Message-----
> From: Dipak Jha [mailto:dipak.jha@p...]
> Sent: Friday, March 14, 2003 3:21 PM
> To: ASP.NET
> Subject: [aspx] High packet count
>
>
> Hi,
>
> I had written to the group earlier too on this but since I did not recieve
> any response and since the problem continues to plague my project, I'm
> narrating the story again.
>
> I've migrated a legacy application, writen in VB-ASP to ASP.NET. The pages
> and business logic are identical. On my local LAN, the ASP.NET application
> is faster and more sclable. But on a WAN (2 LANs connected through a 2
Mbps
> link across a 1000 Kilometers), the ASP.NET application is 1.5 - 2 times
> slower. This led me to capture packets (using a packet capture tool called
> "ethereal") and then count the number of packets transacted per HTTP
> request. I found that though the ASP.NET produced pages are smaller (by a
> factor of 0.75) compared to the legacy pages, the number of packets
> transacted between the client and the web-server is 1.44 times higher
> compared to the legacy application.
>
> Why does ASP.NET transact more in terms of packets exchanged? Is there a
way
> to overcome this problem?
>
> Please send in your views on this. I'm in a real fix and would appreciate
> any help in this regard.
>
> Regards,
>
> Dipak Jha
>
>
>
>

Hi,
    one of the reasons u see the higher number of packets transferred is
because ADO.NET uses a higher footprint than classic ADO and this is because
ADO.NET uses XML behind the scenes for everything

To overcome this problem, u can not use a dataset and instead use datareader
also make sure u turn the viewstate for the datagrid off the drawback is
that u'll have to implement your own paging/sorting algo
asp.net uses postbacks for a lot of things..
 make sure you are using client side validations for uplevel clients.


Regards,
 Naveen Nayak

-----Original Message-----
From: Dipak Jha [mailto:dipak.jha@p...]
Sent: Friday, March 14, 2003 3:40 PM
To: ASP.NET
Subject: [aspx] RE: High packet count

Hi Sakthi,

The pagesize I'm talking about is the size of the actual html pushed to the
browser. And yes, within that html, I can see those encoded strings / view
state information etc that you have talked about.

Regards,

Dipak Jha

----- Original Message -----
From: "Palani, Sakthivel (Cognizant)" <PSakthiv@c...>
To: "ASP.NET" <aspx@p...>
Sent: Friday, March 14, 2003 3:31 PM
Subject: [aspx] RE: High packet count


> did you measure the page size in terms of the html source pushed to the
browser or just the design time html of your aspx pages ?. To maintain view
state of your controls Asp.net sends an encoded string stored in hidden
variables; to the browser which is then decoded by runtime, this might be
the cause for the additional packets generated.
>
> You have to use viewstate of controls selectively to avoid such overheads.
>
> Regards,
> Sakthi.
>
>
>
> -----Original Message-----
> From: Dipak Jha [mailto:dipak.jha@p...]
> Sent: Friday, March 14, 2003 3:21 PM
> To: ASP.NET
> Subject: [aspx] High packet count
>
>
> Hi,
>
> I had written to the group earlier too on this but since I did not recieve
> any response and since the problem continues to plague my project, I'm
> narrating the story again.
>
> I've migrated a legacy application, writen in VB-ASP to ASP.NET. The pages
> and business logic are identical. On my local LAN, the ASP.NET application
> is faster and more sclable. But on a WAN (2 LANs connected through a 2
Mbps
> link across a 1000 Kilometers), the ASP.NET application is 1.5 - 2 times
> slower. This led me to capture packets (using a packet capture tool called
> "ethereal") and then count the number of packets transacted per HTTP
> request. I found that though the ASP.NET produced pages are smaller (by a
> factor of 0.75) compared to the legacy pages, the number of packets
> transacted between the client and the web-server is 1.44 times higher
> compared to the legacy application.
>
> Why does ASP.NET transact more in terms of packets exchanged? Is there a
way
> to overcome this problem?
>
> Please send in your views on this. I'm in a real fix and would appreciate
> any help in this regard.
>
> Regards,
>
> Dipak Jha
>
>
>
>