-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HELP] IoTGW Performance (200dp/s cap) #1484
Comments
@imbeacon Hi, may you explain this two parameters you have in documentation ? whats the difference between the two |
@ashdam if you increase maxPayloadSizeBytes, one MQTT message can have multiple device messages, so measuring performance with this metric is not effective. Moreover increasing this parameter == message count can decrease. |
This has been solved along with many other upgrades, improvements and stabilizations in #1501 |
Describe the issue
We are trying to stress the platform. In order to do this, we started with an OPC-UA async connector with 1000 timeseries declared and "polling" (not subscribe) every second.
Information is sent this way: IoTGateway ==> Edge PE ==> TB PE
We are getting the following information from statistics:
110 events /s, memory size increasing 50 MB, but networkfraffic hasn't reached 1MB/s
Additionally we have verified that we have a 200dp/s cap in pubsub
Do you know what mabe be happening with the cap?
Configuration (Attach your configuration file)
Connector name (If you need help with some connector/converter):
[e.g. MQTT Connector]
Error traceback (If it was raised):
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: