Tilaa Big Disk offers massive storage capacity detached from your VPS. It is available in two variations: Standard (HDD) and Performance (SSD).
However, regardless of the disk type, Big Disk operates as Network Attached Storage. This architecture is fundamentally different from the local storage inside your VPS.
Even though Big Disk SSD is fast, it is still a Network Drive. Every read/write operation requires a round-trip over the network.
This creates Network Latency. Therefore, Big Disk is not suitable for workloads requiring instant file locking or heavy processing, such as databases or web application upload directories.
The Technical Bottleneck: Latency vs. Speed
While the SSD version offers higher throughput (faster file transfers), it cannot overcome the physics of networking. Local storage will always respond faster than network storage.
| Feature | Local VPS Storage (NVMe) | Big Disk SSD | Big Disk HDD |
|---|---|---|---|
| Connection | Internal (PCIe/Local) | Network | Network |
| Latency | Ultra Low (< 0.1ms) | Medium (Network Overhead) | High (Network + Seek Time) |
What NOT to do (Even on SSD)
1. Do not use for Web Application Upload Folders
It is strongly advised not to mount Big Disk as your primary /uploads directory (e.g., wp-content/uploads or storage/app/public).
When a user uploads a file, the server often performs immediate actions: creating temporary files, resizing images, or scanning for viruses. These operations involve many metadata updates and file locks. Performing this over a network drive will cause:
- Slow User Experience: The upload process will feel sluggish or time out.
- File Locking Issues: PHP or Web Server processes may hang waiting for the network storage to confirm locks.
2. Do not run High-Load Databases
Databases require extremely low latency for locking tables and writing transaction logs. Placing a busy database on a network drive results in "I/O Wait" spikes and slow queries.
3. Do not use as Boot Volume
Your Operating System (OS) reads thousands of tiny files during boot. Doing this over a network connection is inefficient and not supported.
When to choose which Big Disk?
Option A: Big Disk HDD (Cost Effective)
Ideal for "Cold Data" that is written once and rarely read.
- Backups: Storing nightly backups (Veeam, Borg, Restic).
- Log Archives: Storing years of historical server logs.
- Disaster Recovery: Keeping a copy of your data safe off-instance.
Option B: Big Disk SSD (Performance)
Ideal for "Warm Data" that involves larger file transfers rather than many tiny interactions.
- File Archives: Storing large datasets (PDF archives, raw video footage) that are only read occasionally.
- Private Cloud Storage: Nextcloud or OwnCloud instances (for storage, not for the database/app itself).
- Docker Volumes: Storing persistent data for containers (provided it's not a heavy database or high-traffic webroot).
Summary
Think of Local Storage as the RAM in your laptop (Instant), and Big Disk as a USB drive attached via a cable.
- Local Storage (NVMe): Use for OS, Databases, Web Applications, and Upload folders.
- Big Disk: Use strictly for storage, archiving, and backups.