Performance Issues (not an ED ad)

Discussion in 'ASP .Net' started by Will, Apr 2, 2008.

  1. Will

    Will Guest

    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
    Will, Apr 2, 2008
    #1
    1. Advertising

  2. 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:...
    > 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
    George Ter-Saakov, Apr 2, 2008
    #2
    1. Advertising

  3. Will

    Will Guest

    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:...
    > > 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

    >
    >
    >
    Will, Apr 2, 2008
    #3
  4. Will

    Will Guest

    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:...
    > > 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

    >
    >
    >
    Will, Apr 2, 2008
    #4
  5. Will

    kpg Guest

    =?Utf-8?B?V2lsbA==?= <> wrote in
    news::

    > 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.
    kpg, Apr 2, 2008
    #5
  6. 32K is ok size....
    Try to turn on the Trace...

    in <systen.web>
    <trace enabled="true" requestLimit="10" pageOutput="false"
    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:...
    >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:...
    >> > 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

    >>
    >>
    >>
    George Ter-Saakov, Apr 2, 2008
    #6
  7. Will

    Will Guest

    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 <systen.web>
    > <trace enabled="true" requestLimit="10" pageOutput="false"
    > 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:...
    > >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:...
    > >> > 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
    > >>
    > >>
    > >>

    >
    >
    >
    Will, Apr 2, 2008
    #7
  8. Will

    Will Guest

    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 <systen.web>
    > <trace enabled="true" requestLimit="10" pageOutput="false"
    > 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:...
    > >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:...
    > >> > 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
    > >>
    > >>
    > >>

    >
    >
    >
    Will, Apr 2, 2008
    #8
  9. 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:...
    > 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 <systen.web>
    >> <trace enabled="true" requestLimit="10" pageOutput="false"
    >> 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:...
    >> >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:...
    >> >> > 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
    >> >>
    >> >>
    >> >>

    >>
    >>
    >>
    George Ter-Saakov, Apr 2, 2008
    #9
  10. 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

    <BODY>
    <script src="http://www.myserver.com/myscript.js>
    HELLO
    <BODY>

    You will not see HELLO until browser loads and executes myscript.js simply
    because that javascript file might build the whole page with document.write
    before HELLO supposed to be displayed...

    My point is that it's one thing to get HTML but another thing to render a
    page... So loading time for myscript.js is important too.

    The best tool to troubleshoot rendering problem is Firefox with FireBug
    add-on.
    So download Firefox then with it go to
    https://addons.mozilla.org/en-US/firefox/addon/1843 and download FireBug.
    go to menu "tools" and enable it.

    PS: I am an IE fan but unfortunately there is nothing even close to FireBug
    for IE.



    George.


    "Will" <> wrote in message
    news:...
    >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 <systen.web>
    >> <trace enabled="true" requestLimit="10" pageOutput="false"
    >> 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:...
    >> >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:...
    >> >> > 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
    >> >>
    >> >>
    >> >>

    >>
    >>
    >>
    George Ter-Saakov, Apr 2, 2008
    #10
  11. Will

    Will Guest

    Oh. No, I did not.
    --
    -Will


    "George Ter-Saakov" wrote:

    > 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:...
    > > 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 <systen.web>
    > >> <trace enabled="true" requestLimit="10" pageOutput="false"
    > >> 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:...
    > >> >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:...
    > >> >> > 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
    > >> >>
    > >> >>
    > >> >>
    > >>
    > >>
    > >>

    >
    >
    >
    Will, Apr 2, 2008
    #11
  12. Will

    Will Guest

    Thanks for all the help. I will have to consider the Firefox option.
    --
    -Will


    "George Ter-Saakov" wrote:

    > 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
    >
    > <BODY>
    > <script src="http://www.myserver.com/myscript.js>
    > HELLO
    > <BODY>
    >
    > You will not see HELLO until browser loads and executes myscript.js simply
    > because that javascript file might build the whole page with document.write
    > before HELLO supposed to be displayed...
    >
    > My point is that it's one thing to get HTML but another thing to render a
    > page... So loading time for myscript.js is important too.
    >
    > The best tool to troubleshoot rendering problem is Firefox with FireBug
    > add-on.
    > So download Firefox then with it go to
    > https://addons.mozilla.org/en-US/firefox/addon/1843 and download FireBug.
    > go to menu "tools" and enable it.
    >
    > PS: I am an IE fan but unfortunately there is nothing even close to FireBug
    > for IE.
    >
    >
    >
    > George.
    >
    >
    > "Will" <> wrote in message
    > news:...
    > >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 <systen.web>
    > >> <trace enabled="true" requestLimit="10" pageOutput="false"
    > >> 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:...
    > >> >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:...
    > >> >> > 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
    > >> >>
    > >> >>
    > >> >>
    > >>
    > >>
    > >>

    >
    >
    >
    Will, Apr 2, 2008
    #12
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. JMaelstrom

    IIS 6 vs IIS 5 ASP.NET Performance Issues

    JMaelstrom, Dec 9, 2003, in forum: ASP .Net
    Replies:
    2
    Views:
    4,661
    shan420
    Apr 30, 2010
  2. John Q. Smith

    SQLServer session state performance issues

    John Q. Smith, Jan 12, 2004, in forum: ASP .Net
    Replies:
    4
    Views:
    3,445
    =?Utf-8?B?Sm9obiBRIFNtaXRo?=
    Jan 16, 2004
  3. smoody

    Performance Issues / ASP.NET

    smoody, Feb 20, 2004, in forum: ASP .Net
    Replies:
    4
    Views:
    555
    Kevin Spencer
    Feb 20, 2004
  4. David Adams

    IIS 6 performance issues?

    David Adams, Jul 6, 2004, in forum: ASP .Net
    Replies:
    0
    Views:
    411
    David Adams
    Jul 6, 2004
  5. Greg Collins [MVP]
    Replies:
    7
    Views:
    378
    Greg Collins [MVP]
    Nov 5, 2004
Loading...

Share This Page