News for hackers. Stuff that matters.
Re:Tmpfs considered harmful by raverbashing on Wednesday September 12, 2012 @09:50AM (#4510627)
Depends on your use case and how much of that complexity you wish to manage

In your case, what could work is having the new run use the same file names as the old run, or coming up with a rotation schedule (so you would keep the latest N runs)

But if having them on /tmp as it is working for you, great, no need to complicate things.

There are also speed considerations, if you're using these files as actual intermediate storage (as opposed to a log/debug dump) it may be interesting to have them written to a different disk (like an SSD)

Re:Tmpfs considered harmful by RobAley on Wednesday September 12, 2012 @10:07AM (#4510700)
In my case, the runs are often run in parallel and in batches of varying sizes, so "same name" or rotation schedules wouldn't work well. They are a kind of hybrid log/storage file (they contain intermediate data sectioned/logged into the actions that created them, like an extremely verbose log). Dedicated SSDs would be very nice, but out of the price budget (i.e. its a zero cost project, run on existing scavanged hardware!).

As you say, /tmp is working well for me, my example was to perhaps illustrate that there are (what I think are) legitimate uses for large files in /tmp.