[zeromq-dev] PUB-PULL Messaging Broker Improve the messaging

[Bernardo Augusto García Loaiza]

 workflow, I think that before to I ask others to deductively answer why
something happens at your desk application  distributed behavior, I
should perform some experiments about of performance and networking
conditions and workload on each peer and the transport protocols used

Any consideration about of how to start with these experiments.

How to can I measure the arrival time of messages on each peer when these
messages departure from their source or origin peer?

Thanks.




Bernardo Augusto García Loaiza
Ingeniero de Sistemas
Estudiante de Maestría en Ingeniería Informática - Universidad EAFIT
http://about.me/bgarcial


On Thu, Mar 22, 2018 at 5:23 PM, Bernardo Augusto García Loaiza <
botibagl at gmail.com> wrote:

> I have implemented this ZMQ Client-Server architecture with the order to
> one message from *Sender* client, this message arrives at other clients *Receiver
> 1, Receiver 2 and Receiver 3.*
>
> This means that the all receivers can see the same data from *Sender*
>
>
> In this architecture, I have python clients and c++ clients. The server is
> coded with Python using pyzmq binding.
>
> The question is: Why on my python clients the message appears faster than
> on my c++ clients?
>
> This is related to the server is coded in Python?
>
> What kind of nonfunctionals considerations should I have to improve the
> performance of the messaging system?
>
> Is possible think in one thread by each message routed to the receiver?
>
> I would meet your considerations about it
>
>
> Bernardo Augusto García Loaiza
> Ingeniero de Sistemas
> Estudiante de Maestría en Ingeniería Informática - Universidad EAFIT
> http://about.me/bgarcial
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20180323/04aba086/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 40833 bytes
Desc: not available
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20180323/04aba086/attachment.png>