Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If I find the perfect solution to something on CPAN, am I gonna make myself impopular if I suggest using extproc_perl?

    Do you know how it compares to PL/SQL when it comes to performance?
    • *impopular*? :-)

      PL/SQL tends to be faster when using its builtin operations. However, Perl is infinitely more flexible, and the availability of CPAN modules make it a winner when it comes to functionality. Once Perl is parsed and compiled, it's pretty fast. Actual speed really depends on what you're doing and how often you do it. The number one bottleneck is interpreter initialization (see mod_perl), but that's a one-time hit especially if you're using app server connection pools or Apache::DBI. And if you're just running something once to process some data, then you probably won't notice the initialization too much.

      After the initialization, your code will run as fast as Perl can run. All of the communication between Oracle and extproc_perl is done via Oracle's IPC mechanisms, which are blazingly fast. The only slowdown you'll see is during operations that are normally parallelized, such as index creation -- Oracle's external procedures are currently single-threaded, so we're kinda stuck there.

      Yikes, that was a mouthful. FYI, I'll be presenting all this stuff in excruciating detail at YAPC::NA this year.