title: Do C# static functions perform better than nonstatic functions, beyond reduced memory usage?
body: <p>I assume that <code>public</code> or <code>private</code> <code>static</code> targets must have reduced memory usage, due to the fact that there is only one copy of the static target in memory.</p>
  
  <p>It seems like because a method is static that might make the method a potential point for further optimization by the CLR compiler beyond what is possible with a non-static function.  Just a flimsy theory though, so I've come to ask you all.</p>
  
  <p>Do <code>static</code> <code>public</code> or <code>private</code> methods provide any increased performance benefit beyond reduced memory usage?</p>
  
  <p>(Note: I'm not interested in responses that talk on the problems of premature optimization. Certainly that's sound advice I follow everyday, but that does not mean optimization is not necessary at times. (double negative!).  Allow me to indulge my curiosity, at the least)</p>