-
Notifications
You must be signed in to change notification settings - Fork 79
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
Bigger Receiving Througput with QoS 1 and 2 #54
Comments
I don't know if it is a bug, but it looks indeed suspicious. I will have a look at our QoS setup code. Maybe there is a bug. |
yes here: QoS 0
QoS 1
QoS 2
|
ok, thank you. I have to have a deeper look at the code. My current hypothesis is: If QoS>0 is set, we first send all messages and receive them afterwards in a complete bulk. If QoS==0 we receive as we sent. |
Can you give me some details on the used broker software? Is it a managed service? Can I setup a instance of that broker? This will help to find the issues with this. |
The broker is a simple eclipse-mosquitto (1.6.12) docker image with default configuration.
|
Hello!
I'm stress testing a broker and and I noticed a lot bigger receiving througput with QoS 1 and 2. Otherwise same parameters.
Broker is on AWS.
No errors, all 100% published/received.
Why is that?
QoS 0
QoS 1
QoS 2
Sorry if is not a bug :)
The text was updated successfully, but these errors were encountered: