Performance Issues (not an ED ad)

My Intranet asp.net/vb app runs "okay" across the LAN, not great, but okay.
Across the WAN, however, performance is unacceptable.

It's not an overly complicated application. I use a few third party
(Infragistics) tools and some standard tools to display a data entry sheet,
accept the values and save them to SQL2005.

Total size of the transferred file is 146k. (View Source...Save as).

VS2005 8.0.50727.762
..Net 2.0.50727
IIS (I don't know how to get the version of this)

--
-Will

Re: Performance Issues (not an ED ad)

Obviously .NET does not care how you hit application across LAN or WAN. It
will work with the same speed.
The only difference is that LAN is faster than WAN so most likely your page
size makes a difference.
To be honest 146K is pretty heavy page.
Try to disable "ViewState" that you do not need. It will reduce the page
size..

George.


"Will" wrote in message
news:29D16CF7-7068-47AD-96D7-E46BC10FE4EF@microsoft.com...
> My Intranet asp.net/vb app runs "okay" across the LAN, not great, but
> okay.
> Across the WAN, however, performance is unacceptable.
>
> It's not an overly complicated application. I use a few third party
> (Infragistics) tools and some standard tools to display a data entry
> sheet,
> accept the values and save them to SQL2005.
>
> Total size of the transferred file is 146k. (View Source...Save as).
>
> VS2005 8.0.50727.762
> .Net 2.0.50727
> IIS (I don't know how to get the version of this)
>
> --
> -Will

Re: Performance Issues (not an ED ad)

Thanks. I disabled viewstate completely and only gained 3k. I must have
something drastically wrong. This may be bigger than anyone here can answer
w/o a lot of code going back and forth.

I will look at the code again and post back.

Thanks.
--
-Will


"George Ter-Saakov" wrote:

> Obviously .NET does not care how you hit application across LAN or WAN. It
> will work with the same speed.
> The only difference is that LAN is faster than WAN so most likely your page
> size makes a difference.
> To be honest 146K is pretty heavy page.
> Try to disable "ViewState" that you do not need. It will reduce the page
> size..
>
> George.
>
>
> "Will" wrote in message
> news:29D16CF7-7068-47AD-96D7-E46BC10FE4EF@microsoft.com...
> > My Intranet asp.net/vb app runs "okay" across the LAN, not great, but
> > okay.
> > Across the WAN, however, performance is unacceptable.
> >
> > It's not an overly complicated application. I use a few third party
> > (Infragistics) tools and some standard tools to display a data entry
> > sheet,
> > accept the values and save them to SQL2005.
> >
> > Total size of the transferred file is 146k. (View Source...Save as).
> >
> > VS2005 8.0.50727.762
> > .Net 2.0.50727
> > IIS (I don't know how to get the version of this)
> >
> > --
> > -Will
>
>
>

Re: Performance Issues (not an ED ad)

I broke my page down to the basics (I can provide details if you care) and it
is now 32K.

I have a System.Web.UI.WebControls.DropDownList which causes an
AutoPostBack. Locally the page loads in < 1 sec. Refreshes in < 1 sec.

Over the WAN the page loads in 3-4 secs. Refreshes take 5-7 secs.

I'm looking for answers but still don't know the questions.

--
-Will


"George Ter-Saakov" wrote:

> Obviously .NET does not care how you hit application across LAN or WAN. It
> will work with the same speed.
> The only difference is that LAN is faster than WAN so most likely your page
> size makes a difference.
> To be honest 146K is pretty heavy page.
> Try to disable "ViewState" that you do not need. It will reduce the page
> size..
>
> George.
>
>
> "Will" wrote in message
> news:29D16CF7-7068-47AD-96D7-E46BC10FE4EF@microsoft.com...
> > My Intranet asp.net/vb app runs "okay" across the LAN, not great, but
> > okay.
> > Across the WAN, however, performance is unacceptable.
> >
> > It's not an overly complicated application. I use a few third party
> > (Infragistics) tools and some standard tools to display a data entry
> > sheet,
> > accept the values and save them to SQL2005.
> >
> > Total size of the transferred file is 146k. (View Source...Save as).
> >
> > VS2005 8.0.50727.762
> > .Net 2.0.50727
> > IIS (I don't know how to get the version of this)
> >
> > --
> > -Will
>
>
>

Re: Performance Issues (not an ED ad)

=?Utf-8?B?V2lsbA==?= wrote in
news:E5F8B797-BC17-46E1-828D-4571D72765CF@microsoft.com:

> I broke my page down to the basics (I can provide details if you care)
> and it is now 32K.
>
> I have a System.Web.UI.WebControls.DropDownList which causes an
> AutoPostBack. Locally the page loads in < 1 sec. Refreshes in < 1 sec.
>
> Over the WAN the page loads in 3-4 secs. Refreshes take 5-7 secs.
>
> I'm looking for answers but still don't know the questions.
>

Just a thought - is it too late to ajax enable the page?

I know this works best when it's decided on 'before' the code is
written, but you apparently have a lot of content/data whatever, so
if performance is an issue you may need to re-think the design.

Re: Performance Issues (not an ED ad)

32K is ok size....
Try to turn on the Trace...

in
traceMode="SortByTime" localOnly="true" />

then see what is going on inside .NET.

If time shown will be the same for WAN and LAN then it's definite connection
speed that makes the difference...

PS: By any chance you did not disable bufferization in .NET. Hope not. It
will make a huge difference with WAN over LAN.


George.


"Will" wrote in message
news:E5F8B797-BC17-46E1-828D-4571D72765CF@microsoft.com...
>I broke my page down to the basics (I can provide details if you care) and
>it
> is now 32K.
>
> I have a System.Web.UI.WebControls.DropDownList which causes an
> AutoPostBack. Locally the page loads in < 1 sec. Refreshes in < 1 sec.
>
> Over the WAN the page loads in 3-4 secs. Refreshes take 5-7 secs.
>
> I'm looking for answers but still don't know the questions.
>
> --
> -Will
>
>
> "George Ter-Saakov" wrote:
>
>> Obviously .NET does not care how you hit application across LAN or WAN.
>> It
>> will work with the same speed.
>> The only difference is that LAN is faster than WAN so most likely your
>> page
>> size makes a difference.
>> To be honest 146K is pretty heavy page.
>> Try to disable "ViewState" that you do not need. It will reduce the page
>> size..
>>
>> George.
>>
>>
>> "Will" wrote in message
>> news:29D16CF7-7068-47AD-96D7-E46BC10FE4EF@microsoft.com...
>> > My Intranet asp.net/vb app runs "okay" across the LAN, not great, but
>> > okay.
>> > Across the WAN, however, performance is unacceptable.
>> >
>> > It's not an overly complicated application. I use a few third party
>> > (Infragistics) tools and some standard tools to display a data entry
>> > sheet,
>> > accept the values and save them to SQL2005.
>> >
>> > Total size of the transferred file is 146k. (View Source...Save as).
>> >
>> > VS2005 8.0.50727.762
>> > .Net 2.0.50727
>> > IIS (I don't know how to get the version of this)
>> >
>> > --
>> > -Will
>>
>>
>>

Re: Performance Issues (not an ED ad)

While I play with Trace can you explain your P.S.?
--
-Will


"George Ter-Saakov" wrote:

> 32K is ok size....
> Try to turn on the Trace...
>
> in
> > traceMode="SortByTime" localOnly="true" />
>
> then see what is going on inside .NET.
>
> If time shown will be the same for WAN and LAN then it's definite connection
> speed that makes the difference...
>
> PS: By any chance you did not disable bufferization in .NET. Hope not. It
> will make a huge difference with WAN over LAN.
>
>
> George.
>
>
> "Will" wrote in message
> news:E5F8B797-BC17-46E1-828D-4571D72765CF@microsoft.com...
> >I broke my page down to the basics (I can provide details if you care) and
> >it
> > is now 32K.
> >
> > I have a System.Web.UI.WebControls.DropDownList which causes an
> > AutoPostBack. Locally the page loads in < 1 sec. Refreshes in < 1 sec.
> >
> > Over the WAN the page loads in 3-4 secs. Refreshes take 5-7 secs.
> >
> > I'm looking for answers but still don't know the questions.
> >
> > --
> > -Will
> >
> >
> > "George Ter-Saakov" wrote:
> >
> >> Obviously .NET does not care how you hit application across LAN or WAN.
> >> It
> >> will work with the same speed.
> >> The only difference is that LAN is faster than WAN so most likely your
> >> page
> >> size makes a difference.
> >> To be honest 146K is pretty heavy page.
> >> Try to disable "ViewState" that you do not need. It will reduce the page
> >> size..
> >>
> >> George.
> >>
> >>
> >> "Will" wrote in message
> >> news:29D16CF7-7068-47AD-96D7-E46BC10FE4EF@microsoft.com...
> >> > My Intranet asp.net/vb app runs "okay" across the LAN, not great, but
> >> > okay.
> >> > Across the WAN, however, performance is unacceptable.
> >> >
> >> > It's not an overly complicated application. I use a few third party
> >> > (Infragistics) tools and some standard tools to display a data entry
> >> > sheet,
> >> > accept the values and save them to SQL2005.
> >> >
> >> > Total size of the transferred file is 146k. (View Source...Save as).
> >> >
> >> > VS2005 8.0.50727.762
> >> > .Net 2.0.50727
> >> > IIS (I don't know how to get the version of this)
> >> >
> >> > --
> >> > -Will
> >>
> >>
> >>
>
>
>

Re: Performance Issues (not an ED ad)

I added Trace to the page instead of the whole app.

The values for the End Render (From First(s)) are as follows:

WAN Client Local
Initial Load 0.0556 0.0587
After Refresh 0.02886 0.0286

The WAN client still says it takes 5-7 seconds for a refresh. Now I'm really
confused.

--
-Will


"George Ter-Saakov" wrote:

> 32K is ok size....
> Try to turn on the Trace...
>
> in
> > traceMode="SortByTime" localOnly="true" />
>
> then see what is going on inside .NET.
>
> If time shown will be the same for WAN and LAN then it's definite connection
> speed that makes the difference...
>
> PS: By any chance you did not disable bufferization in .NET. Hope not. It
> will make a huge difference with WAN over LAN.
>
>
> George.
>
>
> "Will" wrote in message
> news:E5F8B797-BC17-46E1-828D-4571D72765CF@microsoft.com...
> >I broke my page down to the basics (I can provide details if you care) and
> >it
> > is now 32K.
> >
> > I have a System.Web.UI.WebControls.DropDownList which causes an
> > AutoPostBack. Locally the page loads in < 1 sec. Refreshes in < 1 sec.
> >
> > Over the WAN the page loads in 3-4 secs. Refreshes take 5-7 secs.
> >
> > I'm looking for answers but still don't know the questions.
> >
> > --
> > -Will
> >
> >
> > "George Ter-Saakov" wrote:
> >
> >> Obviously .NET does not care how you hit application across LAN or WAN.
> >> It
> >> will work with the same speed.
> >> The only difference is that LAN is faster than WAN so most likely your
> >> page
> >> size makes a difference.
> >> To be honest 146K is pretty heavy page.
> >> Try to disable "ViewState" that you do not need. It will reduce the page
> >> size..
> >>
> >> George.
> >>
> >>
> >> "Will" wrote in message
> >> news:29D16CF7-7068-47AD-96D7-E46BC10FE4EF@microsoft.com...
> >> > My Intranet asp.net/vb app runs "okay" across the LAN, not great, but
> >> > okay.
> >> > Across the WAN, however, performance is unacceptable.
> >> >
> >> > It's not an overly complicated application. I use a few third party
> >> > (Infragistics) tools and some standard tools to display a data entry
> >> > sheet,
> >> > accept the values and save them to SQL2005.
> >> >
> >> > Total size of the transferred file is 146k. (View Source...Save as).
> >> >
> >> > VS2005 8.0.50727.762
> >> > .Net 2.0.50727
> >> > IIS (I don't know how to get the version of this)
> >> >
> >> > --
> >> > -Will
> >>
> >>
> >>
>
>
>

Re: Performance Issues (not an ED ad)

I mean you did not do Response.buffer = false;

If you did it will dramatically decrease speed especially over slow
networks. Basically every your Response.Write will take long time to
execute.



George.


"Will" wrote in message
news:A4A8402F-0EF5-4AAA-A3EA-491AAB48FFF6@microsoft.com...
> While I play with Trace can you explain your P.S.?
> --
> -Will
>
>
> "George Ter-Saakov" wrote:
>
>> 32K is ok size....
>> Try to turn on the Trace...
>>
>> in
>> >> traceMode="SortByTime" localOnly="true" />
>>
>> then see what is going on inside .NET.
>>
>> If time shown will be the same for WAN and LAN then it's definite
>> connection
>> speed that makes the difference...
>>
>> PS: By any chance you did not disable bufferization in .NET. Hope not. It
>> will make a huge difference with WAN over LAN.
>>
>>
>> George.
>>
>>
>> "Will" wrote in message
>> news:E5F8B797-BC17-46E1-828D-4571D72765CF@microsoft.com...
>> >I broke my page down to the basics (I can provide details if you care)
>> >and
>> >it
>> > is now 32K.
>> >
>> > I have a System.Web.UI.WebControls.DropDownList which causes an
>> > AutoPostBack. Locally the page loads in < 1 sec. Refreshes in < 1 sec.
>> >
>> > Over the WAN the page loads in 3-4 secs. Refreshes take 5-7 secs.
>> >
>> > I'm looking for answers but still don't know the questions.
>> >
>> > --
>> > -Will
>> >
>> >
>> > "George Ter-Saakov" wrote:
>> >
>> >> Obviously .NET does not care how you hit application across LAN or
>> >> WAN.
>> >> It
>> >> will work with the same speed.
>> >> The only difference is that LAN is faster than WAN so most likely your
>> >> page
>> >> size makes a difference.
>> >> To be honest 146K is pretty heavy page.
>> >> Try to disable "ViewState" that you do not need. It will reduce the
>> >> page
>> >> size..
>> >>
>> >> George.
>> >>
>> >>
>> >> "Will" wrote in message
>> >> news:29D16CF7-7068-47AD-96D7-E46BC10FE4EF@microsoft.com...
>> >> > My Intranet asp.net/vb app runs "okay" across the LAN, not great,
>> >> > but
>> >> > okay.
>> >> > Across the WAN, however, performance is unacceptable.
>> >> >
>> >> > It's not an overly complicated application. I use a few third party
>> >> > (Infragistics) tools and some standard tools to display a data entry
>> >> > sheet,
>> >> > accept the values and save them to SQL2005.
>> >> >
>> >> > Total size of the transferred file is 146k. (View Source...Save as).
>> >> >
>> >> > VS2005 8.0.50727.762
>> >> > .Net 2.0.50727
>> >> > IIS (I don't know how to get the version of this)
>> >> >
>> >> > --
>> >> > -Will
>> >>
>> >>
>> >>
>>
>>
>>

Re: Performance Issues (not an ED ad)

As you see .NET is working at the same speed with WAN and LAN as expected.

Here is another suggestion (besides making sure Response.Buffer is not set
to false).

The rendering speed...

Although HTML is transferred fast you will not see the actual page in a
browser until all components such as JavaScript and CSS loaded and
executed....

Example

If you have something like