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.

Hackathon Days 2+3: Report 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I mentioned this on #perl6, but I think you missed it -- the high-performance user ("Ilya") may be doing bandwidth-intensive stuff as well -- it's important then to have efficient access to packed data streams.

    This becomes especially important when each data element requires very little computation, but there are a LOT of data elements to go through.

    Hmmm, perhaps this should be a new user type . . . .

    • Lots of calculation and lots of data movement are closely related, but I don't know if they're the same or not. If you're moving so much data that the mere movement of it is a challenge from Perl, actually processing any of it substantially is probably a C-language issue (e.g. mpeg compression).

      Perhaps you could contribute an "Ilya Prime" sub-profile?

      • $ svk diff
        === docs/req/model_users.pod
        ====================================================== ============
        --- docs/req/model_users.pod  (revision 13090)
        +++ docs/req/model_users.pod  (local)
        @@ -103,6 +103,38 @@
           a favorite feature set and stick with it

        +=head2 "Ilya Prime": Intensive Memory Bandwidth User
        +
        +Ilya Prime writes high-performance memory bandwidth-bound code,
        +typically involving either very large packed arrays or "touch once"
        +streaming algorithms that make CPU caches near-usele
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.