Slow Initial Server Response

10,719

Solution 1

After a thorough investigation I discovered that the slow initial Time to First Byte was caused by the database connection string. A period "." was being used for the default server instance name rather than the name of the server being specified. When I changed the period to the server name the TTFB dropped to normal levels.

Thanks very much to all who answered.

Solution 2

IIS7.5 has a plugin which initializes applications and helps reduce the slower performance of that initial load after an IIS restart or app pool recycle.

You can also install this via the Web Platform Installer.

Once installed you should notice there is a new option in the Advanced Settings of each IIS application pool allowed you to control this action on an application pool basis.

application initialization settings

Share:
10,719

Related videos on Youtube

Mike Poole
Author by

Mike Poole

More than two decades of commercial web development across the entire stack. Clients include the largest enterprises and many, many government agencies. I enjoy teaching others and as such had the opportunity to teach web development at Edinburgh University and SharePoint development through my book. I am constantly learning new skills having recently undertaking an Android nanodegree and now learning Python (who isn't!). For fun I like to play chess, go sailing and hillwalking.

Updated on September 14, 2022

Comments

  • Mike Poole
    Mike Poole over 1 year

    We have an ASP classic website running on an IIS 7.5 dedicated server with no other sites running on it.

    The wait time for the homepage on the initial request is about 5.2 seconds but then subsequent wait times are a much more acceptable 133ms.

    I am not sure why this is happening. Is there an app pool setting that I can check?