How to handle high CPU load on MetaDefender Core server?

Hardware factor

When encountering high CPU utilization on your %product_name% server, first verify that the system meets the minimum hardware requirements for your respective engine package:

  • $link[page,367630,Windows system requirements,windows-recommended-system-configuration]
  • $link[page,367630,Linux system requirements,linux-recommended-system-configuration]

As a reference, you can see $link[page,367633,auto$] metrics (throughput, CPU utilization, processing time), to estimate required hardware resource that could meet your throughput and processing time requirements.

Software factor

If the system meets the requirements, there are other software factors that can affect CPU utilization, as outlined in the $link[page,367548,MetaDefender Core Performance Tuning Guide,software-factors]:

  • %product_name% version: older versions may not have the best performance optimization.
  • Engines and database: processing with more engines and using local PostgreSQL database can increase CPU usage on the server.
  • Configuration: more thorough scan settings (such as deep scans, archive scanning) require more hardware resources.
  • File characteristics: more complex file types require more resources to scan and process.
  • Concurrent scans: higher concurrent scans require more resources.
  • Integration method: how %product_name% is integrated into other applications (e.g. via APIs) can influence performance.

Details on these software factors, and software tuning guide to avoid high CPU utilization can be found in the $link[page,367548,MetaDefender Core Performance Tuning Guide,metadefender-core-application-tuning].

You can export MetaDefender Core’s $link[page,367903,processing history] as CSV format, and analyze which file types are being processed the most, for example:

If you see that there are many archive file types, you may need to adjust $link[page,367581,archive handling limits,archive] (max recursive level, max total extracted files, max total size of extracted files) in %product_name% workflow.

  • A higher limit means %product_name% needs to dig deeper to process these files, so incrementally reduce the limit and observe CPU utilization.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
On This Page