Bigger Receiving Througput with QoS 1 and 2

[inovex]

Bigger Receiving Througput with QoS 1 and 2

[hikhvar]

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.
Do you have the corresponding sending throughput?

[AlmostRuio]

yes here:

QoS 0

# Publishing Throughput
Fastest: 25 msg/sec
Slowest: 12 msg/sec
Median: 18 msg/sec

# Receiving Througput
Fastest: 126 msg/sec
Slowest: 23 msg/sec
Median: 77 msg/sec

QoS 1

# Publishing Throughput
Fastest: 18 msg/sec
Slowest: 9 msg/sec
Median: 14 msg/sec

# Receiving Througput
Fastest: 49685 msg/sec
Slowest: 71 msg/sec
Median: 550 msg/sec

QoS 2

# Publishing Throughput
Fastest: 16 msg/sec
Slowest: 8 msg/sec
Median: 12 msg/sec

# Receiving Througput
Fastest: 31005 msg/sec
Slowest: 69 msg/sec
Median: 567 msg/sec

[hikhvar]

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.
The fact that sending with QoS>0 is slower that QoS==0 supports this hypothesis. Moreover this result is expected since QoS > 0 should be slower since it requires more communication between sender and broker.

[hikhvar]

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.

[AlmostRuio]

The broker is a simple eclipse-mosquitto (1.6.12) docker image with default configuration.
Docker compose:

broker:
    image: eclipse-mosquitto
    ports:
      - 1883:1883