MQTT: Mosquitto broker queue test - #5
Open
jrbenito wants to merge 8 commits into
Open
Conversation
File was based on zmq_pubsub, now most converted to use Mosquitto. Still need to implement listen function.
-still need to rewrite listen method.
Instead of rewriting listen function, wrote a blocking recv function to behave similar as ZeroMQ recv.
Rewrite the subscribe to avoid error when subscribing. This allowed listen to work correct with test_client script.
Bench now runs test_client with "--mqtt" option and plot results together ZeroMQ and Redis results
Gnuplot was not working while running bench.py. The .png files were being generated as null. The fact is bench.py was calling gnuplot from working directory and not from output directory. The result was gnuplot did not find that .dat files with data to plot. This fix avoids manual generation of .png file by issuing gnuplot command inside output directory.
Owner
|
Awesome! Thanks a lot for sharing this. Like the other contributions, I won't actually merge this into the repo - but I'll link to it from the README and in the blog post as well for anyone who's interested. Great stuff. |
|
Can anyone post the results of this test here? |
Contributor
Author
|
this was done long time ago, I don´t have results anymore. Consider run it by yourself, the setup is pretty simple. Keep in mind that mosquitto broker had evolved ever since and results may differ. rgds, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi Stephen,
If you want to take a look and compare, I wrote some code to test_client.py and also a mqtt_pubsub.py wrapper in order to include MQTT protocol to the comparison you made. It is meant to be used with Mosquitto broker.
I run a test on a Ubuntu 12.04 64 bits, Intel Core2quad Q9550. Everything installed as your Readme suggests, Redis and Mosquitto from official Ubuntu repository with default configuration. My results point out that ZeroMQ is still quicker and that it takes advantage (like redis) from multiple core while Mosquitto is still quicker than Redis its results clearly shows that broker is not multi-core aware. I will run this on another machine, a Phenon X4/X6 to have something to compare with.
Anyway, I had not so experienced with python and if someone finds any issue with mqtt_pubsub.py I will gladly merge corrections. I have no experience with Go language so I still did not write any Go client to Mosquitto.
Thanks for your work, I would not get so far without your original code. This study will be decisive in a research I am conducting here.
Regards,
Benito.