Optimizing your script(s) based on revision and early pre-tests can help ensure that you're running an effective performance test.
Here are steps you should take:
- Use JSR233 + Groovy + compilation key instead of BSF
- Disable your script listeners. Especially the ones mentioned below as they consume a lot of memory:
- Graph results
- Comparison assertion visualizer
- View results in tree
- View results in table
- Run in a non-graphical user interface (GUI) mode
- Optimize your Java configuration to meet your needs
- Use CSV as your output format
- Use the regular extractor rather than XPath
- Minimize the usage of assertions
- Minimize the usage of post-processor elements
- In the egular expression extractor, minimize the data that has to be extracted
- Generate reports after test is completed
- When you have a higher number of users, use multiple machines
- Try to increase JMeter's heap memory