Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

Large files can be uploaded via the REST API, or projected into the repository using filesystem federation.  Transfer times for uploading to the repository via the REST API are about the same as copying using NFS, and moderately faster than using SCP.  Uploading via the REST API to a federated filesystem is significantly slower and requires a large temp directory capacity.

...

Based on the tests below, we believe arbitrarily-large files can be ingested and downloaded via the REST API (tested up to 1TB).  The only apparent limitations are disk space available to store the files, and a sufficiently large Java heap size.Note:

Note
To enable fast access to large files, it is necessary to set "contentBasedSha1" : "false".  Otherwise the repository will run a SHA1 on the content for identification that could take

...

hours when reaching into the range of > 50Gb.  For more on this benchmarking see: Design - LargeFiles.

...

Based on the tests below, we believe arbitrarily-large files can be projected into the repository via filesystem federation and downloaded via the REST API (tested up to 1TB).  The only apparent limitations are disk space available to store the files, and a sufficiently large Java heap size. 

...

Based on the tests below, we believe arbitrarily-large files can be uploaded and downloaded via the REST API, using either repository storage or a federated filesystem (tested up to 1TB).  The only apparent limitations are disk space available to store the files, temp directory capacity, and a sufficiently large Java heap size. 

...