Do C# static functions perform better than nonstatic functions, beyond reduced memory usage?

Question

I assume that public or private static targets must have reduced memory usage, due to the fact that there is only one copy of the static t

Answer 1

This is a little bit off-topic, but none the less important.

The choice of making methods static or instance should not be based on execution time (which anyway seems not to matter). It should be based on whether the method operates on an object. For instance, all the Math.* methods are static while e.g. (most) String.* methods are instance since they operate on a String instance. My personal philosophy: a good design should make up for the few cycles that may be saved elsewhere.

Another view on the subject: I recently worked with a guy who had been told that static methods are evil because they take us back to the dark age of procedural programming and thus shall be avoided at all costs. This resulted in weird examples of classes that required instances for access to methods that had absolutely no interest in the internals of the object.

Phew, it felt good to get that from my hearth.