Bureaucrats, cc_docs_admin, cc_staff
2,232
edits
Storage and file management: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(add link to "Transferring data") |
No edit summary |
||
| Line 33: | Line 33: | ||
== Best practices == <!--T:9--> | == Best practices == <!--T:9--> | ||
* Regularly clean up your data in the scratch and project spaces, because those filesystems are used for huge data collections. | |||
* Only use text format for files that are smaller than a few megabytes. | * Only use text format for files that are smaller than a few megabytes. | ||
* As far as possible, use scratch and local storage for temporary files. For local storage you can use the temporary directory created by the [[Running jobs|job scheduler]] for this, named <code>$SLURM_TMPDIR</code>. | * As far as possible, use scratch and local storage for temporary files. For local storage you can use the temporary directory created by the [[Running jobs|job scheduler]] for this, named <code>$SLURM_TMPDIR</code>. | ||
* If your program must search within a file, it is fastest to do it by first reading it completely before searching. | * If your program must search within a file, it is fastest to do it by first reading it completely before searching. | ||
* If you no longer use certain files but they must be retained, [[Archiving and compressing files|archive and compress]] them, and if possible copy them elsewhere. | * If you no longer use certain files but they must be retained, [[Archiving and compressing files|archive and compress]] them, and if possible copy them elsewhere. | ||
* For more notes on managing many files, see [[Handling large collections of files]], especially if you are limited by a quota on the number of files. | * For more notes on managing many files, see [[Handling large collections of files]], especially if you are limited by a quota on the number of files. | ||