Is it possible to trick PDF file formation?

[DanRRRR]

As we all know NAND flash drives have limited endurance. Most popular consumer ones typically based on TLC technology (3 bits per cell, endurance only around 1000 writes) allow to write only around 600 TB per 1 TB drive. As a result if you run PIC codes on your own hardware and use flash drives you will experience wear, and eventually crashes and other problems every few years. My typical runs generate 1-3TB per day so I change NVMe drives every year or two. Unfortunately there are almost no more resilient drives based on MLC (two bits per cell, endurance 10k writes) and the SLC ones (1 bit per cell 100k writes) of large capacities are too expensive. They will eventually appear but this tech is just too new now.

Is it possible to trick the EPOCH such a way that it will think that it is doing its SDF output but actually it does not writes anything into storage?
Or make such a way that it will write onto RAM region (which has no wear problems) instead of drive storage and delete the file after writing?

/** I do not need SDF files at all because write all PIC major variables directly into separate files which ideally EPOCH would also allowed (or allowed more standard methods of storing like HDF5) but unfortunately there is no such options

[TomGoffrey]

You could use something like tmpfs and write files to RAM.

[DanRRRR]

Thank you for the idea, Tom!