| aep | title | author | status | type | category | created | completed | updated | resolution | roadmap |
|---|---|---|---|---|---|---|---|---|---|---|
15 |
Persistent Storage |
Greg Osuri (@gosuri) |
Final |
Standard |
Core |
2021-04-16 |
2021-04-23 |
2024-12-01 |
major |
By default, Akash offers temporary storage that is wiped clean upon worload restarts. To maintain data integrity across reboots, we propose enabling persistent storage functionality, which ensures that information written to the disk remains intact.
Akash's persistent storage feature ensures data continuity throughout a lease's duration. Deployments can restart or relocate within a provider while maintaining access to stored data, as the provider assigns a host-mounted volume to the deployment.
This capability mirrors storage solutions in public cloud environments, significantly enhancing various deployment scenarios. Future updates may explore data persistence across multiple leases, further expanding functionality. For more information, refer to the documentation.
Moreover, we suggest increasing resource limits for each deployment. Services will be able to utilize up to 256 CPUs individually, with a total of 512 CPUs per deployment, 32 TB of storage, and 512 GB of memory. Persistent storage is essential for many workloads, including large-scale blockchain node hosting and applications relying on databases.
All content herein is licensed under Apache 2.0.