Skip to content

Performance level

The performance level decides how quickly a signal change travels between your PLC and the simulation in the browser, and how much computing time that costs. You set it once for the gateway and can change it while everything is running.

There are two levels:

  • Low - bundles signal updates and saves CPU. Fine for monitoring.
  • High - fast signal exchange for commissioning. The default.
LowHigh
Signal sending in CONNECTAfter a change, waits the full publish interval before sendingSends the first change after an idle period at once; further changes are bundled until the publish interval has passed
Signal sending in the browserBundles changes on a 16 ms gridSends the first change after an idle period at once, then bundles on the 16 ms grid
Windows timer resolutionDefault of about 15.6 ms1 ms
PLCSIM Advanced cycleAt least 10 ms, even if you configured lessThe configured cycle (default 2 ms, minimum 1 ms)
CPU costLowestA little more

The timer resolution is a Windows setting of the CONNECT process. Low releases it, so CONNECT does not keep Windows at 1 ms unnecessarily. On other operating systems it has no effect.

Measured Windows wait times for a requested 1 ms wait (500 samples on one machine, CONNECT as a tray application):

Timer settingMedian95th percentileMaximum
Default (Low)15.5 ms16.1 ms16.8 ms
1 ms resolution (High)1.0 ms2.0 ms2.8 ms

These are wait times inside CONNECT, not response times of the whole loop.

Rough guide values for the whole loop, from a PLC output through CONNECT and the model back to a PLC input:

  • Low - around 40 to 70 ms on average, with single values above 100 ms depending on the interface.
  • High - shorter, because waits drop out: the bundling in CONNECT and in the browser no longer delays the first change, and CONNECT’s timer no longer rounds a short wait up to about 16 ms. Expect around 25 ms on average, rarely more than about 30 ms.

These are guide values, not a guarantee. They apply to PLCSIM Advanced; other interfaces have their own polling or publish cycle (for example an OPC UA subscription interval, an MQTT publish interval or the cycle a Modbus or S7 interface reads at), and that cycle adds to the loop. The values also depend on the PLC cycle, your computer, the browser and the model. Measure your own setup with Response time, once at each level.

Use whichever way fits your workflow. The change takes effect immediately; you do not restart CONNECT, its interfaces or the simulation.

  • In the viewer - open the CONNECT page and click Low or High in the Performance row. If the buttons are greyed out, the line below them says why, for example that no gateway is connected or that the gateway is too old to support levels.
  • As a command - run connect.performance.set with {"performance": "High"}, for example through web_execute from an AI assistant.
  • Over REST - send PUT /config/performance with {"performance":"High"} to the gateway. GET /health returns the current value. See REST and WebSocket API.

The level belongs to the gateway, not to a model. Every connected browser tab sees a change at once. It is saved and survives a restart of CONNECT.

  • Monitoring or a demo with a slow PLC cycle - Low. Lowest CPU load, and updates arrive bundled.
  • Commissioning logic and virtual commissioning - High.

The simulation applies a PLC signal in its next step, and the steps follow the browser’s frame rate. Whether the simulation keeps running in a hidden tab is a separate switch, Keep simulating in background. If it is off, the simulation pauses when the page is hidden, at either level.

Even with it on, browsers may slow a tab that is covered or in energy-saving mode, and a long frame (a heavy model load, a large selection) delays everything for that duration. For measurements and demos, keep the tab visible and in front.

The performance level changes how fast signals travel. It does not change how the model is simulated.

Continuous simulationDES
What the level changesHow soon a PLC signal reaches the model and how soon the model’s answer reaches the PLCThe same, for a DES model that exchanges signals with a PLC
Simulation stepUnchanged: the model rate (60 Hz unless the model says otherwise)Unchanged: events are processed as before
ResultsMotion and logic are calculated the same way at both levels; only the reaction time to PLC signals differsEvent order and results are the same at both levels
When High mattersPLC loops and virtual commissioningOnly when a PLC is connected to the DES model and its reaction time matters

See DES simulation modes for the playback modes.