Hashed Files

This summary sheet derives is data from the Hashed File Data sheet which you can inspect for further details.

Note that you can read more about S2PX’s treatment of Hashed Files here.

Prevalence of Hashed Files in Jobs - Summary

The Summary graph at the top simply identifies the proportion of Jobs which make use of one or more Hashed Files stages. Jobs are categories as …

The next summary graph identifies, for each Hashed File reference, whether that reference is…

RED Shared between Jobs or Job invocations. Identifies Hashed File instances in a Job which are…
- Reading but not writing, meaning the Hashed File has been generated by an upstream Job, or
- Writing but not reading, meaning the Hashed File is being produced for consumption by a downstream Job, or by a different invocation of the same Job.
ORANGE Hashed File Appending Data. Identifies Hashed File instances which append data, meaning the Hashed File already existed at the point of Job invocation, and is being appended to produce data for consumption by a downstream Job, or by a different invocation of the same Job.
YELLOW Hashed File Synchronisation. Identifies Hashed File instances accessing the same Hashed File from multiple stages on the same canvas, potentially introducing a synchronisation issue that could require manual effort to implement in a Parallel environment.
GREEN Hashed File Transient, Exclusive. Identifies ephemeral Hashed Files, seemingly created, written, and read exclusively within the same job, and which appear to be used in a transient manner to act simply as a synchronisation point.

A list which breaks out the Hashed File Usage patterns summary above by Job, ordered by descending frequency of usage.