Performance-impact of empty Page_Load() methods

When adding a new page or user control to an ASP.NET webforms application, the code-behind class contains an empty Page_Load() event handler:

public partial class Default : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {

    }
}

I have an existing web app, where many pages and controls still contain these empty event handlers (they are not used).

Question: Is there any performance impact due to these empty event handlers and should they therefore be removed from all pages and controls?

Please note: I'm not mainly (or not only) concerned about any runtime-overhead, due to the empty event handler being called. I also wonder about any overhead while the page (markup) is JIT-compiled (because the event handlers have to be wired up to the event开发者_高级运维s - probably using some reflection code).

Update: there was no real answer so far, so I can't accept any of them.

AutoEventWireup is not done at the compile time. When it set to true, the runtime has to look for each of the page event handlers using Delegate.CreateDelegate method for this. Here is a great article which describes this behaviour: Inside AutoEventWireup.

There is a similar question here: What is the performance cost of autoeventwireup?

While the stack frame must be adjusted to enter and leave your method (and doing nothing) as opposed to simply calling the base implementation (in this case System.Web.UI.Page ), the performance impact is incredibly small and most likely unmeasurable so you should be fine.

I'm fairly certain Page_Load occurs whether it's there or not. Much like PreRender occurs, or Page_Init.

Removing it will do nothing for performance.