gen_server mzb_time terminated with reason: {timeout,{gen_server,call,[mzb_interconnect,get_director]}} about vmq_mzbench HOT 3 CLOSED

Hi @KrlosWd thanks for asking... I have seen those kind of errors. I can't give you a single reason why.

A couple of observations:

• why use 14 nodes for 35k publishers only? you could use way less nodes
• you can go faster than 40 rps for worker setup, if you want (and have configured enough acceptors)
• 35k msg/s into a single queue will likely just block that queue. If your use case is massive fan-in to a single consumer, you'd most likely have to user additional strategies.

from vmq_mzbench.

Hi @ioolkos, thanks for your quick answer,
As for your observations, it is worth to mention that I'm benchmarking the open source MQTT broker named mosquitto since I implemented some changes for some experiments I'm conducting for a research project, the problem with mosquitto is that it is single threaded. So having that in mind:

• why use 14 nodes for 35k publishers only? you could use way less nodes
  The VM I have access to have limited CPU (actually a single core), thus I found out that having more than 3k publishers per node will cause the following error:

14:15:06.228 [error] emulator Error in process <0.10270.0> on node '[email protected]' with exit value:
{{badmatch,{error,timeout}},[{cpu_sup,measurement_server_init,0,[{file,"cpu_sup.erl"},{line,497}]}]}
14:15:51.412 [error] emulator Error in process <0.10277.0> on node '[email protected]' with exit value:
{{badmatch,{error,timeout}},[{cpu_sup,measurement_server_init,0,[{file,"cpu_sup.erl"},{line,497}]}]}
14:16:18.462 [error] emulator Error in process <0.10280.0> on node '[email protected]' with exit value:
{{badmatch,{error,timeout}},[{cpu_sup,measurement_server_init,0,[{file,"cpu_sup.erl"},{line,497}]}]}
14:17:09.136 [error] emulator Error in process <0.10283.0> on node '[email protected]' with exit value:
{{badmatch,{error,timeout}},[{cpu_sup,measurement_server_init,0,[{file,"cpu_sup.erl"},{line,497}]}]}

• you can go faster than 40 rps for worker setup, if you want (and have configured enough acceptors)

Since mosquitto is single threaded, the number of connections it can accept in one second is pretty limited. With 40 rps per node I have a total of 560 rps, however I think I could go higher than that, but I'm using this number as a safe rate in the mean time.

• 35k msg/s into a single queue will likely just block that queue. If your use case is massive fan-in to a single consumer, you'd most likely have to user additional strategies.

Each node uses a different topic, so I actually have 14 queues but I'm open to suggestions :D

from vmq_mzbench.

Thanks for your details @KrlosWd !
Keep us posted on your testing progress and any results with Mosquitto (which of course is incredibly powerful on 1 core)

from vmq_mzbench.