Websocket load test utilising high cpu and memory of the VM used for testing

Question

I'm running api load tests with a script that's a combination of REST and websocket APIs. The resource utilisation of the VM where I'm using jmeter to execute load tests is much higher than before incorporating the websocket APIs. I wanted to understand if that's normal if I'm doing something wrong. The transaction rate of the test is 2000 transactions per minute by 2000 users. Other than the API samplers I have a few JSR223 samplers. I was wondering whether they could be the reason. But they process pretty simple functions, (creating or renaming a variable each iteration). Has anyone been in a similar situation and is there any way to optimise the script resource utilisation.

Ivan G · Accepted Answer · 2025-03-07 15:15:23Z

0

Using JSR223 Test Elements is fine as long as you:

Use Groovy language
Cache compiled scripts

So it might be the case the plugin is consuming resources, you can use a profiler tool to see what exactly consumes resources

It might also be a good idea to follow JMeter Best Practices and recommendations from 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article

answered Mar 7 at 15:15

Ivan G

3,1771 gold badge10 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Websocket load test utilising high cpu and memory of the VM used for testing

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related