Open jizhenfang opened 6 years ago
Hi,
3000 tps is pretty impressive for the Java client! Moving to nio could be a good improvement further down the line, but it might require significant refactoring in a very sensitive part of the client so it's currently not at the top of our priority list. You're of course welcome to try moving to it yourself if you like?
hi,I have meet a performance issue in paho. It's only 3000 tps from paho client to rabbitmq (MQTT broker), but the cpu , memory ,io usage is very low. I have saw the paho's resource code and The CommsReceiver use socket.getInputStream() . I think maybe here is the problem. Is it right?