0

I have configured Jmeter for database load testing, and have been using the CLI to test load on my redshift database. i have increased the memory heap but the same problem remains heap

Below is the Error I am getting even after increasing the heap size to 5 gigabytes.

WARNING: package sun.awt.X11 not in java.desktop
Creating summariser <summary>
Created the tree successfully using //Users/mbyousaf/Desktop/redshit-test/test-redhsift.jmx
Starting standalone test @ Wed Dec 02 14:53:17 GMT 2020 (1606920797442)
Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port 4445
Warning: Nashorn engine is planned to be removed from a future JDK release
java.lang.OutOfMemoryError: Java heap space
Dumping heap to java_pid35596.hprof ...
Heap dump file created [3071802740 bytes in 3.747 secs]
0

Your heap dump is 3 GB only and according to your configuration it should be 5 GB which makes me think that your heap size amendment hasn't been applied.

You can check what exact settings are effective for your JMeter instance by adding i.e. setUp Thread Group to your test plan with the JSR223 Sampler containing the following code:

println('JMeter Java arguments: ')
java.lang.management.ManagementFactory.getRuntimeMXBean().getInputArguments().each { argument -> println(argument)}

this way you will get something like this in the console:

enter image description here

If your setting is applied and you cannot allocate more heap and still cannot conduct the required load the only way I can think of is to get another machine and consider going for Distributed Testing

1
  • yes have added more heap allocation, it still somehow takes a long time to complete the queries but they are being completed now. many thanks :) – Bilal Yousaf Dec 3 '20 at 9:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.