Half a million records for a six-month period suggests that you are bringing in less than 3000 submissions a day, on average. This is not a particularly large number from a flat file perspective -- I wouldn't worry too much about optimization unless you have a practice of really going out of your way to make your code inefficient. :)

I know you've said you don't have access to a database, but sometimes people say that when they mean "I don't have access to an instance of Oracle" or whatever the company uses for production data. Have you considered MySQL? It is pretty easy to install, and has most of the power of a 'full-fledged' commercial relational database. Encryption/decryption aside (because I know very little about such things), having your data stored in a relational database makes the extraction of that data in interesting ways much easier.

Rather than blindly hand over the CSV file or whatever to your customers, I would go a step further and ask, "What do you do with this information?" I find that many times there is some simple task I can do while I still have the data that makes life much easier for my customers.


No good deed goes unpunished. -- (attributed to) Oscar Wilde

In reply to Re: Bad Idea? Questions of performance issues, file locking, and GPG by ptum
in thread Bad Idea? Questions of performance issues, file locking, and GPG by hmbscully

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.