Is OOP always significantly slower than procedural?

Back when I was working on Smalltalk at ParcPlace, we had a saying about Smalltalk that can also be applied to using Objects with Perl:

Smalltalk: A little slower, but a lot sooner.
The point being that the leverage gained from having a well tested class hierarchy (think CPAN) to build on usually wins out over the perceived need to make the code as fast as possible.

Method invocation is 15-20% slower than static function invocation, but performance bottlenecks tend to cluster into small sections of code, allowing selective optimization. If you're up to speed on objects, you'll get to the bottlenecks quicker, and will have more time to profile and optimize.

In reply to (dws)Re: Object Oriented Perfomance by dws
in thread Object Oriented Perfomance by Lexicon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.