Skip to main content

Server Storage Breakdown

The Storage Breakdown feature helps you understand how disk space is being used on your dedicated Application and Database servers. You can view storage consumption by system components, benches, sites, and database tables to quickly identify what is using the most storage.

Note

Storage Breakdown is available for both Application Servers and Database Servers. The information displayed depends on the type of server you are viewing.

View Database Server Storage

  1. Open your Server Overview page.
  2. Click the Storage Breakdown (Pie) icon for the Database Server.
  3. Review the storage distribution by component.
  4. Click a Site Name to view storage usage for individual database tables.

Database Storage Components

  • Operating System – Storage used by Ubuntu, installed software, and system logs.
  • Binary Logs – Database binary logs used for replication, point-in-time recovery, and disaster recovery.
  • MariaDB Core – Internal database files such as ibdata1, ibtmp1, Aria logs, and other files required by MariaDB.
  • MariaDB Slow Log – Stores slow query logs. Frappe Cloud periodically syncs these logs to Elasticsearch and removes them from the server.
  • MariaDB Error Log – Contains database errors and deadlock information. Like slow logs, these are synchronized to Elasticsearch and cleaned up regularly.
  • MariaDB System Files – Additional files created by MariaDB during normal operation, such as recovery logs and diagnostic files.

View Application Server Storage

  1. Open your Server Overview page.
  2. Click the Storage Breakdown (Pie) icon for the Application Server.
  3. Review the storage distribution.
  4. Expand individual benches to view storage usage in a hierarchical tree structure.

Application Storage Components

  • Bench Size – Includes the core files required by the bench, such as application files, logs, public files, and private files.
  • Additional Disk Usage – Includes storage consumed by directories that are excluded from the main bench size calculation, including:
    • env – Python virtual environment files.
    • node_modules – Node.js packages and dependencies.
    • assets – Compiled assets, stylesheets, JavaScript bundles, and other static files.
Why are some folders excluded?

Directories such as node_modules and assets can contain tens of thousands of files. Excluding them from the primary storage calculation significantly improves the performance of real-time storage analysis while still reporting their overall disk usage separately.

Docker Storage

For Application Servers, the storage breakdown includes only active Docker containers and images. Docker metadata, unused images, and unused layers are excluded to provide a more accurate view of the storage currently in use.

Best Practice

Review the Storage Breakdown periodically to identify growing database tables, large binary logs, or benches consuming excessive disk space. Regular monitoring helps prevent unexpected storage shortages and simplifies capacity planning.

Rating: 0 / 5 (0 votes)