You can set limits for data storage and data transfer as a means of monitoring and controlling usage costs on the ScaleX platform. For these options, set a value (in Gibibytes) desired as the target limit,
and percentages of the target limit when you would receive email notifications.
Note: There are no global platform data storage and transfer limits. However, administrators can impose limits on the account level for visibility.
Setting “Enforce” to “OFF” makes a soft limit, in which you will receive an email notification when the limit is exceeded, but does not change whether you can store or transfer more files to the ScaleX platform.
Setting “Enforce” to “ON” makes a hard, or strict limit.
Enforced storage limit
When the storage limit is enforced, cloud files are automatically deleted until your total active storage is less than your target limit. The oldest files uploaded will be deleted first. The deletion procedure runs every hour, such that it is possible to exceed the storage limit by up to an hour. If you exceed the Free tier level of
data storage in this way, even in the presence of a storage limit within the Free tier, you will be charged for the next tier of data storage.
Note that while file storage is tracked in real-time on the ScaleX platform, storage limit notifications are checked every 10 minutes. This means that if you set a limit to facilitate cost control, but exceed your storage limit in the way described above, you may be receiving notifications after your storage limit has already been exceeded.
Enforced transfer limit
If the transfer limit is exceeded and enforced, users will not be able to upload files to nor download files from Cloud storage is a simple and scalable way to store, access,.... Provided that there is no storage limit, or that it is not exceeded, Rescale compute nodes can still upload and download from Rescale Cloud Storage. Data transfer to and from a Compute node on a running job is not added to the data transfer count.
The file transfer total is, generally speaking, calculated upon completion of an upload, with a 1-hour buffer window. In other words, the file transfer size may not be updated for up to an hour after an upload completes. During this window, it will be possible to exceed the transfer limit, even if enforced, assuming that at the time of starting the upload, the transfer size reflected on the ScaleX platform has not exceed the enforced limit. At this point, the size of data that one can upload beyond the enforced limit will depend purely on the user’s upload bandwidth.
If total data transfer exceeds the level of the Free tier in this fashion, the user will be billed at the corresponding usage tier. See this example on a storage usage spike.