Lasernet Performance Data

This page provides performance data that shows Lasernet’s processing speed when doing specific tasks. These tests were performed under the hardware environment described below.

Note

This performance data should be regarded as indicative only. Your Lasernet system’s performance may differ.

This can be due to multiple factors such as hardware specification, software configuration, input data structure, and network parameters (for example, in Microsoft Azure).

Environment

The following sections describe the hardware, Lasernet configuration, and input and output data sizes that were used for these tests.

Hardware

The performance testing was done on dedicated hardware and used two hosts that had the following configuration:

• 1 x Intel i7 8700K 3.7 GHz (4.7 GHz Turbo) 6 Cores (12 Threads)

• 64 GB RAM

• SSD drives

• 1 GB network adapter

These hosts ran virtual machines under the following configuration.

Host 1

Host 2

Lasernet Configuration

Lasernet Config and servers (instances/environments) used Microsoft SQL Server databases on a dedicated server.

All input and output folders were on a Performance File Server on the network.

Microsoft Azure elements like Azure Storage and Azure Service Bus used their standard configuration.

Input and Output Data Sizes

The tests used a variety of input and output file sizes to enable us to compare Lasernet speed across different data sizes.

Input Files

The performance tests for Azure Storage Output used four PDF sizes:

• 100 KB

• 200 KB

• 1 MB

• 2 MB

Note

The page count of the PDF documents is not relevant. Lasernet throughput is determined by file size.

Note

Small input files (4 KB and 14 KB) were used to generate the PDF files uploaded by these tests. The input file size did not affect the test.

Output Files

The performance tests used documents that had the following file sizes and page counts.

Output file size:

• 100 KB

• 200 KB

• 1 MB

• 2 MB

Page count:

• One page

• Multipage (4 pages)

Execution Standards and Measurements

The tests covered the following scenarios:

• Web Server Input for XML > Form Engine with PDF modifier > File Output

• File Input for XML > Form Engine with PDF modifier > File Output

• File Input for XML > Form Engine with DOCX output > File Output

• File Input for XML > Form Engine with PDF modifier > DM Upload module output

• SFTP Input for XML > Form Engine with PDF modifier > File Output

• Azure Storage Input for XML > Form Engine with PDF modifier > File Output

• Azure Service Bus Input for XML format messages > Form Engine with PDF modifier > File Output

• File Input for PDF files > Azure Storage Output

Each combination in the data tables below is considered to be a distinct test. For example, one-page PDF — 100 KB file size, multipage PDF — 1 MB file size, and so on. We ran each test three times under the stated hardware and Lasernet configuration and then calculated the average of the results for that test.

We endeavored to eliminate temporary environmental problems. For example, we paused Windows updates during test execution to prevent background processes from affecting CPU load.

We measured throughput and execution time:

• Throughput was measured in actions per second (a/s).

• Execution time was measured in seconds.

Test Results

The following sections provide version-specific Lasernet performance data, which shows system performance in specified scenarios.

Lasernet 10.8

Web Input Port — XML to PDF Output

Lasernet configuration:

• Web Input Port > Form Engine (PDF modifier) > Output file

• Number of input ports: 1

• User threads: 4

• Number of simultaneous requests: 250

Summary table — throughput [a/s]

File Input — XML to PDF Output

Lasernet configuration:

• File Input > Form Engine (PDF modifier) > Output file

• Number of input ports: 1

• Multithreading/pooling: Enabled

Summary table — throughput [a/s]

File Input — XML to DOCX Output

Lasernet configuration:

• File Input > Form Engine (Dataset > DOCX output) > Output file

• Number of input ports: 1

• Multithreading/pooling: Enabled

Summary table — throughput [a/s]

File Input — XML to PDF DM Upload

Lasernet configuration:

• File Input > Form Engine (PDF Modifier) > DM Upload Module

• Number of input ports: 1

• Multithreading: Disabled and enabled

• Pooling: Enabled

• Autoform DM version: 10.5.0 standalone

• Autoform DM size: Small database (10 million documents)

Summary table — throughput [a/s]

SFTP Input — XML to PDF Output

Lasernet configuration:

• SFTP > Form Engine (PDF modifier) > Output file

• Number of input ports: 1

Summary table — throughput [a/s]

Azure Storage Input — XML to PDF Output

Lasernet configuration:

• Azure Storage Input > Form Engine (PDF modifier) > Output file

• Number of input ports: 1

• Multithreading/pooling: Enabled

Summary table — throughput [a/s]

Azure Service Bus Input — XML to PDF Output

Lasernet configuration:

• Azure Service Bus Input > Form Engine (PDF modifier) > Output file

• Number of input ports: 1

Summary table — throughput [a/s]

Azure Storage Output — PDF Upload

Lasernet configuration details:

• Input Folder (PDF) > Azure Storage Output

• Number of input ports: 1

• Multithreading: Enabled

Summary table — throughput [a/s]