System Requirements

The Glasswall Embedded Engine supports a wide range of architectures and operating systems, operating in two distinct modes: Protect and Export or Import.

General Performance Notes

Resource usage is driven more by the selected operational mode and file complexity than by the underlying system architecture. While performance for Export and Import is generally comparable, the data below reflects results from Export mode.

Memory Requirements

Memory consumption depends on how complex a file is, based on the number and type of elements the engine evaluates. For example, a small but complex Excel workbook with many sheets may consume more memory than a large but simple image file. File complexity scores are included in the engine’s analysis report. In most cases, real files score no higher than 7, with a maximum value of 10. If available memory is too low, processing may fail.

Processing Time

The Glasswall Embedded Engine is designed to process files using a single thread. To make use of multiple CPU cores, run multiple instances of the engine. Best performance is achieved on modern processors.

Export mode usually requires significantly more time to process files than Protect mode.

Example Performance Data

The following tables show typical memory and processing requirements for both synthetic and real files. Tests were carried out using Linux-based Azure instances with 16 GB RAM. In most production environments, Protect mode processes files in less than one second.

Synthetic File Examples

Real File Examples – Protect Mode

Real File Examples – Export Mode