Worth to set directory for temporary files ?

I made this new topic, because I want to know how are users' PC environment.

Temporary(work) files are used for repair mostly. Some users think that using fast HDD drive or ram drive for temporary files may increase the total speed. Technically, it is easy to implement the feature in PAR clients. The problem is free space (available size) of the fast drive. Temporary files are possible to becomes large as same size as all source files.

While repair, "work file" is constructed from available blocks in "damaged file", or is newly created for "missing file" temporary. Even if 1KB of a 100MB file is damaged, the size of "work file" becomes same as original file size (100MB).

For example, there are 6 source files (100MB x6) and 2 PAR files (100MB x2). When 2 source files are partially damaged and 1 file is lost completely, 3 files need to be reconstructed, and 3 work files are created temporary.

Source files:
"complete file 1"
"complete file 2"
"complete file 3"
"damaged file 1" -> "work file 1"
"damaged file 2" -> "work file 2"
"missing file 1" -> "work file 3"

After successful repair, those "work files" will replace "damaged/missing files". So, the max possible required size of a fast drive is "total size of damaged/missing files". This would be same as "total size of source files". If free space of a fast drive is smaller, it is useless. For example, 1GB RAM drive is worthless to repair 2GB damaged files.

Now questions are your typical data size and drive size in PC. How is your total size of source files ? If you use a fast drive for temporary files, how is the free space ? Will you set a folder for temporary file on Option window, if I implement this feature ? or OS's temporary folder should be used by default ? Do you have time to test the speed, when I will make samples ?

	Author	Topic: Worth to set directory for temporary files ? (Read 354 times)
0 Members and 1 Guest are viewing this topic.