For environments running on Cloud Next technologies, file system utilization metrics are temporarily unavailable and will be added back as soon as possible.
This table displays information about how your environment stores and handles requests for media files uploaded to your application by website visitors, administrators, and developers.
File metrics
Graph | Description |
|---|---|
CPU usage and memory usage for the environment’s infrastructure, as a percentage of the total available. This graph is not available for Cloud Platform Professional subscriptions. | |
Storage for your application’s file system, as a percentage of your available storage capacity. | |
Line chart of the amount of storage used by your application’s file system, as compared to the total amount of available storage. |
Troubleshooting
Use the information in this section to help you troubleshoot file system-related issues with your Cloud Platform application.
CPU and memory usage:
The metrics in this graph can be used to determine how close to capacity your file system infrastructure is, and are often impacted by traffic levels, the number of files associated with your application (especially in cases where there are too many files in a single directory), the size of the files associated with your application, or the frequency of read/write/delete activity on your file system. Although Acquia monitors for infrastructure impairment, file system infrastructure can continue handing file requests even when CPU and memory resources are at or near capacity. If you notice that your file system tier is routinely hitting CPU or memory capacity, you can take the following steps to reduce resource utilization or diagnose the root cause:
If the CPU or memory spikes are associated with traffic, increasing your application’s external (Varnish®) caching settings, including implementing or optimizing Drupal caching. This action can significantly reduce CPU and memory consumption.
CPU and memory spikes may also be associated with activities that involve large numbers of files, or files sized greater than 100 MB. This includes infrastructure where files are being read from, deleted from, or written to directories that contain more than 1,000 files.
Use an Application Performance Monitoring service (such as New Relic) to identify if the spikes in CPU or memory are associated with specific page requests or modules that invoke large numbers of files, or files that are sized greater than 100 MB.
Storage % used and Storage used:
For environments running on Acquia’s Cloud Classic infrastructure, your applications will cease to operate normally once file system storage reaches 100%. Acquia recommends that customers remain under 90% storage utilization at all times, and that they should monitor the rate that their infrastructure is filling up. At 95% usage, Acquia will perform an emergency proactive upsize for Cloud Platform Enterprise customers whose environments are not yet running on Cloud Next technologies. However, if you want to schedule an upsize before your infrastructure reaches capacity, create a Support ticket. The Cloud Next infrastructure can dynamically scale storage capacities based on need.