Slow start to default page

Discussion in 'ASP.NET / ASP.NET Core' started by daviddixon, Jun 22, 2005.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Hi, I have noticed that first requests to my website www.dxnuk.com is very slow - the page is a very smal ASPX page that loads a image using HTML.

    I've noticed that all first requests to my sub-apps are slow to start aswell. I don't think it's my applications because of my default page.

    Is it that DiscountASP.net is hosting too much one server or do they not have enough bandwidth ?

    David
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    ASP.NET compiles the application when the file is first load. This is normal behavior.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. Hi,


    ASP.Net compiles are the reason, as Bruce said. If you want to speed things up, concider not using an aspx page for the deault page of your web application. It all depends on what you're doing, but it may be that you don't need server-side work done on that first page. If it's not a big job, try putting together the first page as a simple html page and see if that helps.


    I'm still somewhat new to this, but as understand it, it's only when a application needs to recomplie the dll, that the process is slowed a good deal. Often, it's only the occasional user that will have to wait for the new compile. You'll need to look at how your app functions to see if you can minimize the recompiles. Also, you need to look at how often you are running back and forth to the server in you applications.If youtrack curser moves serverside, for instance, that's way too many trips back and forth. As you said your pages only are slow the first time, I'd feel confident it's the compiles. Hope it helps, BRN..
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page