General Performance Tip: Performance Impact of Sealing Attributes

When crafting custom attributes, Microsoft advises sealing them to enhance performance. In my coding standards manual, I advocate sealing any class not intended for inheritance, primarily to convey the class’s intent. However, do sealing attributes actually result in improved performance?

Benchmark Results

These benchmark tests demonstrate that the performance difference between sealing and not sealing attributes is negligible, with both options resulting in a memory allocation of 24 bytes.

I maintain my recommendation: any class not intended for inheritance should be sealed for robust class design.

This is how I have it setup checking for this issue in my EditorConfig: dotnet_diagnostic.CA1813.severity = suggestion

Pick up any books by David McCarter by going to Amazon.com: http://bit.ly/RockYourCodeBooks

One-Time
Monthly
Yearly

Make a one-time donation

Make a monthly donation

Make a yearly donation

Choose an amount

$5.00
$15.00
$100.00
$5.00
$15.00
$100.00
$5.00
$15.00
$100.00

Or enter a custom amount

$

Your contribution is appreciated.

Your contribution is appreciated.

Your contribution is appreciated.

DonateDonate monthlyDonate yearly

If you liked this article, please buy David a cup of Coffee by going here: https://www.buymeacoffee.com/dotnetdave

© The information in this article is copywritten and cannot be preproduced in any way without express permission from David McCarter.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.