What are the performance implications of marking methods / properties as virtual?

Question

Question is as stated in the title: What are the performance implications of marking methods / properties as virtual?

Note - I\'m assuming the virtual methods will <

Answer 1

Typically a virtual method simply goes through one table-of-function-pointers to reach the actual method. This means one extra dereference and one more round-trip to memory.

While the cost is not absolutely ZERO, it is extremely minimal. If it helps your program at all to have virtual functions, by all means, do it.

Its far better to have a well-designed program with a tiny, tiny, tiny performance hit rather than a clumsy program just for the sake of avoiding the v-table.