When a hit is received in IIS, it will eventually forward it to ASP.NET. I have this in my entry point:

Public Class WebForm
    Inherits System.Web.UI.Page

    Sub Page_Init(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Init

Can someone tell me, in the situation IIS would queue a load of hits, if in such situation Page_Init() would be executed immediately (which means the hit is still in the queue but at least the Page_Init() has been fired) or this can only happen as soon as IIS is processing the hit from the queue?

I would assume, and always thought, the last mention is what happens. Basically, if 1000 hits are being received in IIS in the same second, that IIS will process what it can, based on its configuration, and will stack in a queue a load of hits. And, then, that load of hits will not reach this code until IIS starts processing it.

Is this pretty much your understanding as well?

The reason I ask is that I am looking the elapse response time from this point and we have an increase in the response time since two days. We just verified SQL Server and everything is ok. This is fully optimized. So, if my response time numbers are higher since two days, it can only means this would then be related to the processing time of hit in my application, thus all those SQL Server requests. And, assuming that, it would then be a mystery as to know why SQL Server is suffering because of more hits reaching IIS. I had assumed IIS, in the event it would receive too much hits, would simply put them in a queue, thus the hit will not be processed right away, and that would never impact the actual processed hits in regards to SQL Server processing time.