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.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.