C++

1783 readers

1 users here now

The center for all discussion and news regarding C++.

Rules

Respect instance rules.
Don't be a jerk.
Please keep all posts related to C++.

founded 1 year ago

MODERATORS

lysdexic

[email protected]

Nihili0

The Performance Benefits of Final Classes - C++ Team Blog (devblogs.microsoft.com)

submitted 1 year ago by lysdexic to c/cpp

2 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 1 year ago (1 children)

tl:dr; making a class final allows the compiler to save a vtable lookup in some (limited, slightly artificial) places where it couldn't before. No actual performance measurements.

I am sceptical. I'd understood vtable lookups to be extremely cheap on modern architecture; usually cheaper than the if / switch statement you'd have to write as an alternative if you weren't using inheritance. And for really performance-sensitive code, you would never have used virtualized classes anyway. I'd like to see some proper performance results before mangling code and making maintenance difficult.

[–] lysdexic 4 points 1 year ago

I am sceptical. I’d understood vtable lookups to be extremely cheap on modern architecture; usually cheaper than the if / switch statement you’d have to write as an alternative if you weren’t using inheritance.

They are relatively cheap, but I think cheap does not mean free and some references mention a performance hit that can be as high as 7%.

And for really performance-sensitive code, you would never have used virtualized classes anyway.

Yeah, because of this performance hit.

One of the cool things about this article is the fact that it points out how adding 'final' can magically get rid of that performance hit.