Impact of Microsoft Defender Scanning on Automation Studio Rebuild and Transfer Times

Disclaimer

Any changes to Microsoft Defender configuration, or to antivirus software in general, should always be discussed with and approved by your local IT department.
The measurements presented in this article are based on a single, dedicated project. Performance impact may vary depending on project size, structure, system configuration, and installed software.

Introduction

This article summarizes test results evaluating the impact of Microsoft Defender real-time scanning on Automation Studio (AS) rebuild and project transfer times. The goal was to quantify performance differences when the project directory is scanned versus excluded from scanning.

Test Setup and Methodology

The tests were performed on a real project. The following methodology was used to ensure repeatable results:

  • Five rebuild attempts per scenario.

  • After each rebuild, the project was uploaded to AR Sim.

  • The first rebuild after starting Automation Studio was excluded from evaluation due to initial warm-up effects.

  • The -profile option was enabled during rebuild to measure timing.

  • Only one Automation Studio instance was running.

  • Background applications running on Windows:

    • Outlook

    • Microsoft Teams

    • Excel

  • Average CPU load at rebuild start: approximately 25%.

Two Automation Studio versions were tested:

  • Automation Studio 4.12

  • Automation Studio 6

Two scenarios were compared:

  • Project located in a standard folder (scanned by Microsoft Defender).

  • Project folder added to the Microsoft Defender exclusion list (not scanned).

Project Characteristics

The tested project contained the following components:

  • mapp View: 17 pages

  • mapp Motion: 9 axes

  • Safety configuration

  • 26 application tasks

Performance Results

:file_folder: Standard Folder (Microsoft Defender Scanning Enabled)

Automation Studio 4.12

Attempt Rebuild Time [s] Time from “Waiting for differences…” to “Transferring transfer module” [s]
1 86 49
2 81 42
3 86 28
4 82 27
5 90 48
Average 85 38.8

Automation Studio 6

Attempt Rebuild Time [s] Time from “Waiting for differences…” to “Transferring transfer module” [s]
1 48 35
2 48 37
3 53 45
4 48 19
5 46 19
Average 48.6 31

:file_folder: Folder Excluded from Microsoft Defender Scanning

Automation Studio 4.12

Attempt Rebuild Time [s] Time from “Waiting for differences…” to “Transferring transfer module” [s]
1 43 5
2 44 4
3 40 4
4 41 4
5 41 4
Average 41.8 4.2

Automation Studio 6

Attempt Rebuild Time [s] Time from “Waiting for differences…” to “Transferring transfer module” [s]
1 37 2
2 36 2
3 36 1
4 38 3
5 38 2
Average 37 2

Same results placed as a picture for better overview

Relative Improvement

Metric AS 4.12 AS 6
Rebuild time reduction 51% 24%
Transfer preparation time reduction 89% 94%

Analysis

Excluding the project folder from Microsoft Defender scanning resulted in significant performance improvements:

  • The time required to generate differences and start the transfer was reduced:

    • AS 4.12: approximately 38.8 s → 4.2 s

    • AS 6: approximately 31 s → 2 s

  • Rebuild times were also notably shorter:

    • AS 4.12: 85 s → 41.8 s

    • AS 6: 48.6 s → 37 s

The most pronounced effect was observed during the transfer preparation phase, indicating that file access and comparison operations are strongly impacted by real-time scanning.

Productivity Impact

For Automation Studio 4.12, the combined rebuild and transfer time was reduced by an average of 77 seconds per cycle. Assuming 50 transfers per day over a work week, this corresponds to a time saving of approximately:

  • 19,250 seconds per week

  • ~5.3 hours per week

While the measurements focused on full rebuilds, the reduced transfer preparation time also benefits regular project uploads, leading to additional time savings during daily development and commissioning work.

Summary

The tests clearly show that excluding Automation Studio project directories from Microsoft Defender real-time scanning can have a substantial impact on rebuild and transfer performance. The improvement is especially significant for transfer preparation, but compilation times also benefit. For workflows involving frequent rebuilds and downloads, this configuration change can lead to measurable productivity gains.

:folded_hands: Thanks colleagues from B&R Poland for this measurements and sharing results with us

14 Likes

Request to describe MS Defender impact in AS Help will be created.

6 Likes

Thanks @kovarj for this performance test!
I knew that real-time analysis software (Microsoft Defender or other AV softwares) had an impact on AS compilation, but I had never taken the time to run these tests!

1 Like

During the migration to AS6, we also noticed (once again) that exceptions for the AS6 installation folder can have an impact on compilation times.
We had already suspected this because we had conducted tests with AS4 years ago and reached the same conclusion

mappView, in particular, seems to benefit greatly when real-time monitoring is not performed.
I can’t present our results here as neatly as @kovarj or repeat the tests easily, but regarding the installation folder, our results were as follows:

Please note:
Our HMI is a bit larger than 23 Contents and also includes some (compound) widgets, etc.


We experienced a reduction in total compilation time (full rebuild) from around 3min 11s to about 1min 23s,
so about 56% performance improvement!
Most of the performance was gained while building/linking the mappView application.


For this reason, in addition to the project folders, we have added the following paths to the exceptions:

  • c:\BrAutomation (AS4.x)
  • c:\Program Files (x86)\BRAutomation\ (AS6.x)
  • c:\Program Files\BRAutomation\ (AS Code, we never tested the impact)



Note: We don’t use Microsoft Defender but Trend Micro Apex One.

6 Likes

The project folder on the MS Defender whitelist also has a significant positive impact on the VM.

Also, all prebuild and postbuild scripts need to be whitelisted, including system powershell/python folders.

2 Likes