Ready API 1.8.0 Memory Usage
This is an issue I've been fighting against for some time, and have yet to find a solution to. In all of my testing, over time, ReadyAPI / SoapUI NG ends up using 4+GB of memory. I have a laptop with...
Forum Discussion
The project XML file is just shy of 10MB in size, and all other projects were closed. I had even closed ReadyAPI and re-opened it before running the test.
Have you had any luck solving SoapUI memory issues? I've been having these issues ever since using SoapUI. It seems to just hold on to memory throughout the test case no matter what I do (disable transaction log, groovy script to clear cache). It's a huge issue to have while running large or complex test cases, and SmartBear seems be be doing nothing to solve it.
At least when you advertise your product, let potential customers know of these huge limitations to your software. And before someone links me to the "Improve memory usage" page, I've already done all of those things, and it still build memory up throughout the whole test case, quickly going from 1GB to 12GB and failing to continue due to max heap size error. My company will definitely be looking into other options for API testing if this glaring and significant issue can't be addressed.
gallowdp: I've yet to find a solution outside of either running the memory intensive projects from commandline without the gui, since that seems to take up much less memory, or monitoring memory usage in task manager and restarting as necessary. I've also found that ReadyAPI stores expanded-states for all projects/test suites/test cases per workspace. I wrote a powershell script that'll clean that up. That ends to save me a LOT of memory.
Thanks @msiadak I run the large test cases via testrunner in the command line but it still builds up RAM quickly. Would you be willing to share any more info on your powershell script to clean up unneeded memory? I'm not familiar with writing or running powershell scripts but if you have any resources I'd be very grateful.
Powershell is a scripting tool mainly on windows machines, and I use it to keep my Workspace clean and open. It helps with memory usage over time but will not help with memory usage during a test run. The powershell script I wrote helps with when ReadyAPI starts to open slower and slower.
As for memory consumption during test runs, I've also used a "System.gc();" call in a groovy script in some of my heavier hitting tests to try to garbage collect on the fly.