JAWS Policies

JAWS Fair-Share Policies

We are committed to ensuring equitable access to JAWS resources for all users, which is why we have implemented JAWS Execution Throttling that facilitates our fair-share policies.

These policies are designed to manage resource allocation on multiple layers, ensuring that no single user can overload the system. Below are the specifics of our two-layer control system:

Run-Level Throttling (Per User, Per Site)

• Maximum concurrent runs: 200

• Queueing behavior: Additional runs submitted beyond this limit are automatically held in ready state.

• Processing: Queued runs will be launched as soon as active runs complete.

Task-Level Throttling (Per Workflow)

• Maximum concurrent tasks: 300

• Queueing behavior: Any task exceeding this limit is queued within Cromwell.

• Processing: Queued tasks begin executing once active task slots become available.

JAWS Purge Policies

To manage storage effectively, input files (located in the JAWS Staging Area) and Cromwell execution directories (workflow_root) are automatically removed after 10 days.

However, don’t worry—if your run was successful, JAWS will have already transferred the output data to the JAWS Team directory.

For more detailed information on how to find the output data, please refer to JAWS Teams.