Chariot Bridge Performance Testing

Chariot MQTT Server
1

Hi All,
Has anyone done any performance testing on the Bridge component of Chariot?

So far, I have been successfully Bridge raw/unfiltered production data over to our development environment as shown below. This allows us to modify and test any of our UNS/filtered data and bindings prior to apply those in production (MQTT Engine in Dev act like the Site System in Prod).

image
image800×633 59.9 KB

The bridge is carrying sparkplug data and configured for one direction only, so there is no writing back to prod from dev (yes, this does require refresh prod when required as rebirth requests don’t go through which is accepted). It’s been good for a few sites now, but the latest site has lots of tags (35,000) and the bridge connection seems to be dropping and reconnecting all the time. For testing, I setup another MQTT Engine on the same Site Gateway (shown with the blue dashed box) and it doesn’t seem to have any issues. So, I’m assuming Engine/Transmission is fine and its just bridge with the problem?
For some pressure testing, I have setup 3 folders each with 10,000 analog tags each changing every second (count to 60). It seemed to be more stable when each 10k was on a different GroupID/NodeID compared to the same GroupID/NodeID/DeviceID. But still wasn’t perfect.

Any tips, suggestions, learnings greatly appreciated.

Ignition v8.1.48, Engine/Transmission v4.0.32, Chariot 2.6.0. All running in AWS.

Cheers,

2

I should note we don’t recommend using bridging for Sparkplug. Specifically, Will Messages are not handled properly across the bridge and can result in missed NDEATH and STATE messages. I also see you’ve opened a ticket with Cirrus Link support. I think we’ll probably need to take a look at logs to see what is going on with the bridge. Also, there have been quite a few updates to Chariot since 2.6.0. It is likely worth updating.