Agreed, speed isn't the primary concern of the challenge. Two reasons I'm looking specifically at this end of things though:

1) Most of the existing teams are now down to blending results, requiring multiple usage of algorithms before the final blend is performed. In the interests of keeping this process fairly sane, storing and retrieving the data efficiently seems logical given it will be accessed repeatedly.
2) Trying to follow what I perceive to be some form of good practice. No point writing code based around one data access method and then discovering I've got to re-write half of it just because I've changed how the data is stored.

In reply to Re^2: Netflix (or on handling large amounts of data efficiently in perl) by Garp
in thread Netflix (or on handling large amounts of data efficiently in perl) by Garp

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.