Performance testing of chatbot using jmeter

[Srikar1]

Hi,

We have a virtual chat assistant that needs to be tested for performance.
We are using jmeter and testing the websocket's performance . When we run a test plan with 30 odd threads, the first few users get a proper response, but once the response times go beyond 30s or so, the websocket connections are closed automatically - at the same time, when we try to open the app on the front end, we do get a very late response.

We have provided a very generous timeout value on jmeter as well, but for some reason, the connections are getting closed when the response time goes beyond 30s.

Has anybody else faced this issue before? how do we proceed with the performance tests here?

Developers have checked their logs too, and there really are no errors on their end as well, it's just that the bot is taking a very long time to respond - around 60/70s, and jmeter's timeout value isn't taking any effect(the same timeout does work well with other platform bots though), so we are wondering if this is anything specific to servicenow platform?

[Ct111]

Are chats getting closed or the timeout limit is modified .

As per docs: "Virtual Agent and Live Agent conversations that are abandoned by requesters remain open until they are automatically closed by the scheduled job, Time Out Abandoned VA Conversations. This job runs hourly each day. The default timeout period for abandoned Virtual Agent and live agent conversations is two hours (7200 seconds). The Time Out Abandoned VA Conversations job runs hourly to find and close any conversations that have been open longer than the default (or configured) timeout period.".

For more detailed information read this link : https://docs.servicenow.com/bundle/rome-now-intelligence/page/administer/virtual-agent/concept/va-open-conversations.html

There are properties present which decides when to timeout ,plz chk from above link if that has been modified or set in your instance.

Mark my Answer as CORRECT and HELPFUL if it helps.

[Srikar1]

Hi @creativethinker , 

in our case, Snow bot is giving a response in around 70s or so, 
but jmeter is closing the websocket connection at 30s even when the jmeter timeout value is set at 80s.

And we know it's not an issue at jmeter's end, because we have used the same timeout configuration for bots of other platforms. This is something specific to jmeter and Snow bot i guess