Re: Recording asynchronous request/response times

On 26 May 2015 at 12:34, nmodin <[email protected]> wrote:

>
> Now if we forget about reality (GC, number of machines etc), this seems to
> be what I need to do if I read the docs correctly:
>
> Grinder WS load test <http://goo.gl/Tyri9R>
>
> Am I going in the right direction here or did I miss the target completely
> ?
>

That looks about right. You may want to also put a sequence number in the
payload to uniquely identify each message if you want to also confirm that
every message is received.

Also, you may want to carefully consider edge cases, i.e. when everyone is
subscribed to the same message stream (one to many) as well as when
everyone is subscribed to different messages streams (many to many). In the
first case you may find that if the web socket server is poorly designed
(e.g. it iterates serially through the subscriber list) the latency
difference between the first client obtaining the message to the last
client obtaining the same message is significant.

Regards,
Gary

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

_______________________________________________
grinder-use mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/grinder-use