I'm assuming you have memory to burn and don't care about power failures. You'll need to consider if your files' sizes could eventually scale past the point where they won't fit on your ramfs since it may be a pain to rectify this when it actually happens (e.g. you may have to add more ram, fix code, or move it to a disk fs). Obviously, handling this with a disk fs is easier since you can give it a large amount of space ahead of time.

Also, sometimes you'll see little/no significant benefit over using a fast local disk filesystem. Ram filesystems still have to simulate creates/reads/writes/unlinks/etc and, depending on your access pattern, disk filesystem caching can make huge differences.

In reply to Re: Using ramfs to process files by bluto
in thread Using ramfs to process files by jalewis2

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.