Hello @Mark Pope ,
welcome to this moderated Azure community forum.
Let me recap the outcome in an answer.
Based on the conversation it seems the test tool for generating the MQTT messages seems the source of this erratic metrics:
I don't think MQTT Explorer was designed to sustain high workloads over extended time.
By using native MQTT clients as seen in this post, the sawtooth pattern disappeared.
If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.