Possible Duplicate:
Do sealed classes really offer performance Benefits?
My team is wrestling with the sealed class debate internally and I would like to simplify the debate down to a matter of design and get the performance myth off the debate agenda.
Can anyone post some code that demonstrates a performance boost introduced by declaring a class as sealed? At 20 million virtual method calls per second I cannot see much benefit, perhaps 1 or 2 milliseconds on 10 million iterations but even then I am not sure because the result jumps around. This applies to debug and release runs.
p.s. I follow some of the John Skeet received wisdom about the benefit of sealed class design, particularly when software is delivered across a team or org boundary and/or classes are packaged component style in an assembly.
