Forum Discussion
5 Replies
- nmraoChampion Level 3
It is really difficult to comment without knowing the usage of yours.
Couple of suggestions:
1. Close the unused projects.2. Use the tool to design the tests and execute the tests using "READYAPI_HOME/bin/testrunner" utility in command-line mode.
3. Use appropriate heap settings.
You can also look at the documentation regarding the optimizing memory settings:
https://support.smartbear.com/readyapi/docs/testing/best-practices/memory-usage.html- PrakashKannanContributor
Thanks for the suggestion. I tried memory management mentioned. Still it does not work. I think that having the huge test history will be the reason for this. When I disable the 'Test History' in preference , it is faster. Badly I need test history to review my failures on each run.
- groovyguyCommunity Hero
I run into this quite often as well. While not a solution, I have a potential bandaid. I have a project that I use as a test-bed for various groovy script projects. It's small and I usually always have it open. I have a groovy script in there that runs the following code:
System.gc();
I run this whenever I see ReadyAPI using more than a few gigs of memory and sometimes it can help me lessen how many times I have to close and re-open the program.
Related Content
- 12 months ago
- 9 years ago
- 6 years ago
- 12 years ago