Summary

The performance of the synchronisation process in the Report Engine was improved by these steps:

• The synchronisation of those items was optimised (affects all computers regardless the number of processors):
  • Links from archives to equipment groups
  • Variables included in archives
  • Efficiency class models
  • Links from variables to equipment groups
  • Meanings of variables
• The synchronisation now uses parallel computing where feasible (computers with more processors may benefit more than computers with less processors depending on the number of projects included in the synchronisation):
  • First, those items are synchronised in parallel with one task per item:
    • alarm/event classes
    • alarm/event group
    • users
    • equipment models
    • global project language table
    • project metadata
  • Then, the project contents are synchronised in parallel. Each project is synchronised in one task and each task processes those items in that order:
    • shift recording tables
    • variables
    • state lists
    • archives
    • project language table
  • After the project contents, those items are synchronised in parallel with one task per item:
    • efficiency class models
    • sankey diagrams
    • waterfall models

Description

The performance of the synchronisation process in the Report Engine was improved by these steps:

• The synchronisation of those items was optimised (affects all computers regardless the number of processors):
  • Links from archives to equipment groups
  • Variables included in archives
  • Efficiency class models
  • Links from variables to equipment groups
  • Meanings of variables
• The synchronisation now uses parallel computing where feasible (computers with more processors may benefit more than computers with less processors depending on the number of projects included in the synchronisation):
  • First, those items are synchronised in parallel with one task per item:
    • alarm/event classes
    • alarm/event group
    • users
    • equipment models
    • global project language table
    • project metadata
  • Then, the project contents are synchronised in parallel. Each project is synchronised in one task and each task processes those items in that order:
    • shift recording tables
    • variables
    • state lists
    • archives
    • project language table
  • After the project contents, those items are synchronised in parallel with one task per item:
    • efficiency class models
    • sankey diagrams
    • waterfall models