WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@bltierney
Copy link

Updated the data transfer documentation to reflect recent changes in SSH and Globus usage, including last update date, transfer methods, and additional setup steps for large datasets.

Tried to make it more clear on when/why/how to use Globus.

Suggest moving the Globus stuff to a different page.

Updated the data transfer documentation to reflect recent changes in SSH and Globus usage, including last update date, transfer methods, and additional setup steps for large datasets.
When in doubt, start with **SSH-based transfer** — it requires minimal setup and uses your existing TACC credentials.
**Globus**, on the other hand, has its own authentication system and requires additional setup steps, [outlined below](#globus).

However, SSH-based transfers are often **slow on high-latency paths**. If you need to move **large datasets (e.g., over 500 GB)** across network paths where the **round-trip time (RTT) exceeds 10 ms**, we recommend using [Globus](#globus) instead. More information about performance issues with SSH-based tools can be found at [fasterdata](https://fasterdata.es.net/data-transfer-tools/say-no-to-scp/). By default, Globus also performs file-level checksum verification, which helps detect data corruption—especially important when transferring large datasets.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "more information" needs to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants