Re: Recording asynchronous request/response times

Hi Gary,

Thanks for the quick response.

I guess we are in that unfortunate place where we do want to see what
happens to latency (and stability) under peak horizontal loads. In this
case about 500K open web sockets on the server side, so I need to reach
about 50K concurrent web sockets per grinder agent server spread over 10
machines, and then
check the latency for request/response messages sent over those web sockets.

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 ?


Cheers,
Niklas


On Tue, May 26, 2015 at 11:56 AM, Gary Mulder-3 [via Grinder] <
[email protected]> wrote:

> Hi Niklas,
>
> On 26 May 2015 at 08:16, nmodin <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=9079&i=0>> wrote:
>
>> Hi all,
>>
>> I need to record the time between requests and responses for a web socker
>> server I have and can't really figure out how to achieve this. I have a
>>
>
> The Grinder is more designed for pull testing than the push testing
> required for web sockets. If you want to test the horizontal scalability of
> your web sockets you need to get a lot of threads subscribed to your web
> socket and then wait for messages. Depending on the number of sockets, you
> may find that if you send a lot of messages (> 50 per Grinder process)
> simultaneously to your test harness then all the test threads will need to
> wake up at the same time, which causes thread contention and possible GC in
> your test harness. See
> http://grinder.sourceforge.net/g3/garbage-collection.html for details on
> how to monitor and tune GC.
>
> If you want to test latency and not scalability of your web sockets, you
> could import your small java client into The Grinder as a callable class
> and generate time stamps as part of the web socket payload you are
> injecting. On the receiving thread look at the time stamp to calculate how
> long it took from send to receive. You can use a custom statistic to log
> the latency (
> http://stackoverflow.com/questions/23452976/how-to-add-custom-statistics-in-grinder
> ).
>
> Of course you probably want to know the latency of your web sockets when
> you have your peak web socket connections. In the end you may spend a lot
> of time confirming your test harness is not the bottleneck. One solution to
> this is to use a lot of agents, e.g. run them in the cloud.
>
> 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
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=9079&i=1>
> https://lists.sourceforge.net/lists/listinfo/grinder-use
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://grinder.996249.n3.nabble.com/Recording-asynchronous-request-response-times-tp9078p9079.html
>  To unsubscribe from Recording asynchronous request/response times, click
> here
> <http://grinder.996249.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=9078&code=bm1vZGluQGdtYWlsLmNvbXw5MDc4fDE5MjcwNzgzNTQ=>
> .
> NAML
> <http://grinder.996249.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://grinder.996249.n3.nabble.com/Recording-asynchronous-request-response-times-tp9078p9080.html
Sent from the Grinder - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
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