What is the Queue Mechanism on Metadefender Core?
This article applies to all MetaDefender Core V4 and V5 releases deployed on Windows or Linux systems.
MetaDefender Core V4 and V5 come equipped with a queue mechanism designed to streamline and manage high-volume data processing (i.e. file scans).
The article below outlines the basic functioning of the MetaDefender Core queue mechanism.
The main topics include:
- Queue mechanism
- Queue size
Queue mechanism
MetaDefender Core manages its processing tasks in a queue.
Each item in the queue is handled by a Workflow (a thread) on the system. MetaDefender Core starts processing the queue on a ‘first come first served’ basis. However, this doesn't facilitate determination of the run-time for overall processing.
MetaDefender Core uses a maximum of a quarter (25%) of its maximum queue size for archive processing (this applies to all archives processed at a time, not to each one).
This means that, if you send only one archive file into the queue, the archive extraction will fill the queue up to only 25% of the queue size. It does this not only to leave room for further file submissions, but also to provide parallel processing capacity.
Queue size
The default queue size is set to 500.
The number of items in the queue can be extracted from the results of the REST API call GET /stat/nodes.
To increase or decrease this queue value, please read How Do I Configure the Maximum Queue Size in MetaDefender Core.
If you require further guidance around MetaDefender Core’s Queue Mechanism, please follow these instructions on How To Create a Support Package, before creating a support case or chatting with our support engineer.