Possible duplicate:
Do sealed classes really offer performance benefits?
My team is struggling with closed class debates inside, and I would like to simplify the discussion down to the design issue and get the performance myth from the debate agenda.
Can someone post some code demonstrating the performance improvement introduced by declaring the class as sealed? With 20 million virtual method calls per second, I donβt see much benefit, maybe 1 or 2 milliseconds per 10 million iterations, but even then I'm not sure because the result is skipping. This applies to debug and release runs.
ps I am following some of John Skeet's who have gained wisdom about the benefits of a sealed class design, especially when software comes across the org command or border and / or classes - this is the package style of the component in the assembly.
camelCase
source share