I wouldn't categorise OO-Perl as all-caps-with-emphasis slow. In practical terms, it's just an extra argument to your functions, which just happen to be in a different namespace.

Here's a simple benchmark that reveals a maybe 6-10% penalty for using OO without any optimizations. 
use warnings;
use strict;

use Benchmark qw[ cmpthese ];

package Banana;

sub new {
        my $class = shift;
        return bless({ @_ }, $class);
}

sub peel {
        my ($self) = @_;
        my $x;

        foreach (keys %$self) { $x += $self->{$_}; }

        $x;
}

package main;

sub peel {
        my ($banana) = @_;
        my $x;

        foreach (keys %$banana) { $x += $banana->{$_}; }

        $x;
}

cmpthese(10_000,{
        oo_peel => sub { my $banana = Banana->new( foo => 10, bar => 1
+5);
                                for (1..250) { $banana->peel(); } },
        pr_peel => sub { my $banana = { foo => 10, bar => 15 };
                                for (1..250) { peel($banana); } },
});

[download]
I've found that while using an object-oriented approach might be slow at the outset, having a good framework does make optimising easier.

In reply to Re^3: performance - loops, sub refs, symbol tables, and if/elses by tadman
in thread performance - loops, sub refs, symbol tables, and if/elses by jaa

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.