To ensure optimal performance and cost-efficiency, our platform provides a certain amount of local storage included with each compute instance you create. However, exceeding this storage limit can impact your workflow and results. This guide will help you understand how local storage limits work and how to manage your storage usage effectively.

Instance Types Review

Local Storage Limits

• Notebook Instances: Each notebook instance comes with a fixed amount of local NVMe storage, which varies depending on the instance type you choose. This storage is intended for temporary files, code, and data used during your interactive analysis and experimentation.
• Model Training Jobs: For model training jobs, the local NVMe storage limit is calculated per node. If your job uses multiple nodes, the total available storage is the per-node limit multiplied by the number of nodes. This storage is used for storing your training data, model checkpoints, and other intermediate files.
• Online Prediction Endpoints: For model endpoint, the local NVMe storage limit based on the chosen instance type will representative for the total usage storage of all node in an online prediction endpoint. This storage is primarily used for caching model artifacts and handling incoming requests.

Exceeding the Limit

If you exceed the local storage limit for your instance, you may experience the following:

• Read/Write Errors: You might encounter errors when trying to read or write data to the local storage.
• Job Failures: Your training jobs or prediction requests could fail due to insufficient storage space.
• Performance Degradation: Your instance's performance may slow down significantly.

Managing Local Storage

To avoid exceeding the limit and ensure smooth operation, consider these strategies:

• Choose the Right Instance Type: Select an instance type with sufficient local storage for your expected workload. Refer to our documentation for details on the storage capacity of each instance type.
• Optimize Data Usage:
  
  • Stream data from external sources (e.g., S3 buckets) instead of storing it locally whenever possible.
  • Delete temporary files and intermediate results that are no longer needed.
  • Use compression techniques to reduce the size of your data.
• Monitor Storage Usage: Regularly check the storage usage of your instances and jobs using the monitoring tools provided by our platform.
• Upgrade Instance: If you consistently need more local storage, consider upgrading to a larger instance type.