Results 1 to 6 of 6

Thread: ASP.NET problem *RESOLVED*

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Jan 1999
    Location
    California
    Posts
    115

    ASP.NET problem *RESOLVED*

    Ok, I'm not exactly sure howto explain this. Basically, I'm writing an intranet asp.net site to handle alot of the company functions.

    When I goto the site, most of the pages are lightning fast (internal network). Some of the pages that have web controls are are over 32kb, are really slow. I thought it was my code, rewrote it. Didn't help.

    I commented out every single line in the .vb file for the webform on one of the affected files and it still ran slow. I can't explain this problem or why its even occuring.

    I'm running the site (atm) on w2k pro IIS 5.

    Anyone ever heard of a problem like this before?
    Last edited by Ryan; Aug 31st, 2004 at 11:25 AM.
    Ryan French
    Niresoft Incorporated
    http://www.niresoft.com
    [email protected]

  2. #2
    Need more info to be able to help you...

    Are you sure the pages were already compiled when you ran them, because the controls will compile slow the first time each time you have rebuilt the project, restarted the server, etc...

    What version of ASP.NET are you running (ie: 1.0 or 1.1 .net framework)

    Do normal .ASPX pages run slow as long as they do not have controls on them?

    One solution might be to reinstall IIS completely, apply all IIS and related patches, reinstall the .NET framework, and then try to run the same pages again and see if speed is improved.

    Also, check Microsoft's knowledge base under IIS 5 and Windows 2000 for the following keywords:

    slow asp.net pages
    slow ascx
    slow aspx
    (you'll have to come up with some of your own keywords to search under, but you get the point)

    Hope this helps...
    Developer Web Hosting - ASP.NET & PHP
    www.datahostingcenter.com
    15% OFF HOSTING Coupon for Forum Members - Enter:
    vbforums

  3. #3

    Thread Starter
    Lively Member
    Join Date
    Jan 1999
    Location
    California
    Posts
    115
    Are you sure the pages were already compiled when you ran them, because the controls will compile slow the first time each time you have rebuilt the project, restarted the server, etc...
    Yes, I know the first time is going to be slow, so I reload the page a few times to keep a feel for the speed. Slow first, last.

    What version of ASP.NET are you running (ie: 1.0 or 1.1 .net framework)
    1.0

    Do normal .ASPX pages run slow as long as they do not have controls on them?
    Nope, pages run fast when there is no controls on them. Once I drop even a label on a page that is over 32kb, it takes several seconds to load. (***?)
    Ryan French
    Niresoft Incorporated
    http://www.niresoft.com
    [email protected]

  4. #4
    Have you tried running the pages on a Windows 2003 or XP machine under IIS 6?

    Are they still slow on IIS 6?
    Developer Web Hosting - ASP.NET & PHP
    www.datahostingcenter.com
    15% OFF HOSTING Coupon for Forum Members - Enter:
    vbforums

  5. #5

    Thread Starter
    Lively Member
    Join Date
    Jan 1999
    Location
    California
    Posts
    115
    I told the network admin I needed a w2k server up and running as soon as possible. Guess I'll find out if it's maybe a w2k pro problem or not.
    Ryan French
    Niresoft Incorporated
    http://www.niresoft.com
    [email protected]

  6. #6

    Thread Starter
    Lively Member
    Join Date
    Jan 1999
    Location
    California
    Posts
    115
    Welp, looks like I solved the problem. (your solution would of solved it to running it on IIS 6).

    .NET Service Pack 2
    319012 FIX: Delay When You View ASP.NET Page on Windows 2000

    A typical large response to the client creates several smaller buffers in which the data sits before the data is sent to the client. For example, suppose that a response creates five buffers that are 1 kilobyte (KB), 3 KB, 28 KB, 4 KB, and 2 KB in size. The default message size is 32 KB. Therefore, because the total size of these buffers is greater than 32 KB, you must send the buffers one at a time to the client.

    This fix tries to fill up 32 KB messages with these buffers so that you can send larger chunks to the client. The fix is significantly faster. Typically, this fix reduces the average time to last byte (TTLB) time by 200 milliseconds for any page with a response that is greater than 32 KB.


    Link
    http://support.microsoft.com/default...b;en-us;321884
    Ryan French
    Niresoft Incorporated
    http://www.niresoft.com
    [email protected]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width