Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • Come now, we agreed in IRC that the correct way to express the difference was 63% more fastyness.
  • That's really cool. I'm starting to use Moose in some of my applications, but still hesitate using it in CGI (non-FastCGI) scripts, due to that +- 0.20 secs overhead which is still very heavy. Anyway, keep up the great work!
    • A major reason for this recent efforts to cut startup time is actually because we are working with Max Kanat-Alexander (of Bugzilla [] fame) to try and get Moose fast enough to be used in the refactoring/rewriting of Bugzilla. Max is already a fan of Moose and has used it on his (very cool) "All your VCS are belong to us" module VCI [] module. I suspect that by mid-spring you will be able to deploy Moose apps under vanilla-CGI without a worry.

      - Stevan

  • This looks like a good start, keep the fastyness improvements coming.

    Then maybe one day Moose::Tiny may actually be able to compete with Object::Tiny :)
    • Well, we will never beat you on memory usage, but I feel I must remind you that Moose::Tiny is 8% shorter to type than Object::Tiny ;)

      Also, we are really breathing down your neck with our accessors (from the Moose::Tiny POD):

        Benchmarking accessors...
                 Rate moose  tiny
          moose 485/s    --  -19%
          tiny  599/s   23%    --

      And reallly, the difference in speed here is simply because Moose::Tiny c