Instance Sizing

As with all aspects of cloud, performance will vary depending on the resources you allocate.  The instance hosting the CloudDat server must be located in the same region as the bucket.  Larger instance sizes will more often receive a larger share of network bandwidth.  A minimum size of 4 vCPU is recommended.  If performance is not adequate, try a larger instance size.

Reporting

Clients display the progress of uploading data to the CloudDat instance.  It may take several seconds more for the data to then finish being written into storage.  There may be times when object storage takes up to a minute to confirm receipt of the data.

Network

Data cannot move faster than your underlying network and storage hardware.

The instance hosting CloudDat must be located in the same region as the bucket.  Accessing a bucket in a different region than the CloudDat instance will severely limit performance.

Because each transaction must establish communication between the compute instance and storage, it may take a second for each action to start.  If you are uploading large numbers of files to a bucket, consider packaging related files as a ZIP or TAR archive, rather than storing each file as a separate object.  Remember that "objects" are not the same as "files", even though CloudDat will do its best to make them look like files.  See "Objects Are Not Files" for details.

Folders

Folders do not exist in S3-type buckets.

For the purpose of listing remote files, pseudo-folders are displayed by grouping together objects sharing common name prefixes ending in "/".

While pseudo-folders allow you to browse the contents of a bucket as though it were organized into folders, some folder related functions will not work with object storage.

• The "Rename" function cannot be applied to object pseudo-folders.
• The "New Folder" function is silently ignored.
• Empty objects with keys ending in a "/" are ignored.

To use ExpeDat Desktop to upload objects into a pseudo-path that does not yet exist, type the path in the "Remote Prefix" field prior to clicking "Send".

Listing a bucket containing many objects may take a long time, even if they are grouped into pseudo-folders.