IoTIFY Network Simulator
HomeSignupVirtual LabGithub
Search…
Introduction
Walkthrough
Getting Started
Workspaces
Fundamentals
Mapping the IoT device lifecycle
Understanding a Test
IoT Device Model
Protocol Settings
Run Settings
Scenarios
Glob Storage
Additional Helpers
External Libraries
Inbuilt Libraries
IoTIFY Helper Functions
Analyzing Results
Job Summary
Logs
State
Payload
Under the hood
IoT Testing
Overview
Functional Testing
Performance Testing
Security Testing
Test Automation & CI/CD integration
API
Simulation API
Glob APIs
Metrics API
Google Sheets API
IoT platform integration
AWS IoT Connector
Azure IoT
Losant IoT
Google Cloud IoT Core
IBM Cloud
Dweet.io
Create Account
Powered By GitBook
Job Summary
Job summary is an overview of specified runtime parameters and overall test results per iteration.
This tab provides an overall look at the results and a summary for all iterations. The test results per iteration are shown aggregated across all the clients. This gives an idea of how many clients succeeded per iteration.
The next graph shows the client activity over time. Here, you can see how many individual clients were active at the given points in time.
The final graph shows the average, minimum and maximum time it took to send a message to the back-end. This is a true measure of your server performance, as it doesn't count the time it took to generate the message. As we could see, the packet sending latency is fairly maintained consistent with time.
Packet sending latency is highly dependent upon the protocol and transport. E.g. for MQTT QoS 0, the packet sending latency will be lower, as the transmission of the packet is marked completed almost immediately. If the QoS value used is 1 or 2, the sending latency will be much higher for the same test, as higher QoS values require every sent message to be acknowledged for delivery, therefore considerably increasing the latency.
Additional Helpers - Previous
Analyzing Results
Next
Logs
Last modified 6mo ago
Copy link