+1-888-365-2779
Try Now
More in this section

Forums / General Discussions / Slow first access

Slow first access

5 posts, 0 answered
  1. Markus
    Markus avatar
    2763 posts
    Registered:
    25 Nov 2005
    31 Aug 2009
    Link to this post
    I test run standard edtion with SQL Server 2005 in a shared envirement where my web has at least 64 MB RAM reserved for my site.

    The problem is that the first page access always takes very long (internet times - forever) I checked with fiddler2 to see what is going on

    WEbResources.axd 7 KB and 4 KB and 21 KB
    ScriptResources.axd 311 KB, 78 KB, 37 KB, 57 KB, 5 KB, 3 KB, 35 KB, 84 KB, 45 KB

    So there seems to be a total of 680 KB transfered on the first access. This would explain why it would take so long.
    It also seems that if the application pool is recycled it takes an extra 4-8 seconds to get the page ready to be server to my browser.

    Any reason for the large files.
    Any way to cut the files donw and speed up first load?

    Regards Markus
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    31 Aug 2009
    Link to this post
    Hi Markus Berchtold,

    When you restart the application pool it takes several seconds more due to the initialization and serving the worker process. Have you tried using Page caching and Substitution controls. You could find the following posts useful : Performance Optimizations

    Kind regards,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. Markus
    Markus avatar
    2763 posts
    Registered:
    25 Nov 2005
    31 Aug 2009
    Link to this post
    Dear Ivan

    If i am correct page caching would also not help if the app pool is recycled (which is done by my provider 4 times a day)

    Alos if I assume someone not using a normal ISDN connection (not cable or ADSL) it would be very slow because of the 680 KB that need to be downloaded.

    Any idea on how to cut the WEbResources.axd and ScriptResources.axd down?

    Regards Markus

    PS: If you have a site that is visited by 60 clients a minute it is not a problem because 6 hours x 60 clients = 360 clients. One of them has a slow site all other benefit. so only one out of 360 will experiance a slow site.

    But if you have 1 client an hours - then 6 hours x 6 clients = 36 clients. one out of 36 will experiance a slow site.

    Once the first page has been sever all others are quick and caching should work perfekt.

    Regards Markus
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    31 Aug 2009
    Link to this post
    Hello Markus Berchtold,

    You can check whether compilation debug is set to false in your web.config file. You can also optimize your website using RadCompression, OptimizationTips, Optimization Tips for ViewState

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  5. Markus
    Markus avatar
    2763 posts
    Registered:
    25 Nov 2005
    01 Sep 2009
    Link to this post
    I also let a task run every hour getting the homepage.

    This should limit the problems for other users accessing the page.

    Regards Markus
Register for webinar
5 posts, 0 answered