What to Do If Uploading Files Causes CPU Spikes?
This article applies to all MetaDefender Managed File Transfer releases.
If you're noticing CPU spikes when users upload files, it's often due to large individual files requiring significant processing power. Two configuration options in File Settings: "Limit File Size" and "Limit Total File Size" (User Quota) can help manage system resource usage, but they serve different purposes.
Use "Limit File Size" to Prevent CPU Spikes
The "Limit File Size" setting is the most effective way to reduce the risk of CPU spikes during file uploads. This setting restricts the maximum size of individual files that users can upload. By capping the size of each file, you prevent any single upload from consuming excessive CPU resources during processing.
What "Limit File Size" Does:
- Prevents users from uploading files larger than the specified size.
- Helps maintain consistent and predictable CPU usage during file processing.
- Minimizes the risk of performance degradation due to oversized uploads.
Why "Limit Total File Size" Isn’t Enough
The "Limit Total File Size" (also known as User Quota) limits the total storage space a user can consume. While it helps manage overall storage allocation, it does not prevent a single large file from being uploaded, as long as the user's remaining quota allows it. That large file can still trigger a CPU spike during processing.
Recommended Best Practices
- Set a reasonable "Limit File Size" threshold based on your environment’s CPU capacity and typical file usage.
- Monitor CPU usage patterns and adjust limits as needed.
- Combine "Limit File Size" with "Limit Total File Size" for optimal performance and quota management.
By fine-tuning these settings, you can significantly reduce the risk of CPU spikes and ensure a more stable and efficient file upload experience.
If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.