So my loadGen servers are on a virtualized machine. on windows its says memory is 2GB. I tried to change the soapui.bat memory settings to your 2GB recommended settings set JAVA_OPTS=%JAVA_OPTS% -Xms768m -Xmx1500m
but then soapUI does not start. I get the following error
C:\Program Files\eviware\soapUI-Pro-SNAPSHOT\bin>soapui-pro.bat Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine. C:\Program Files\eviware\soapUI-Pro-SNAPSHOT\bin>
you'll run into the same problem with the command-line runner.. just a little later (since it doesn't have the memory overhead of the ui..)
One option could be to add an "Export Errors to Folder" setting to the LoadTest options; a folder to which all errors' contents would be written and then discarded, this would probably preserve a lot of memory (but not all, since the actual LoadTest Log Error Entry would still be there..) how does that sound?
There are a couple of thing which would be useful. 1. Export error to folders sounds good.
2. If you export all the errors to a folder why do you still need the loadTestLog. Can't the log be disabled to preserve memory?
3. When I export the error log, it writes all the assertions to a text file. If the assertions had a name tied to it (e.g LoginStatus) then I can do a word count to see how many of LoginStatus assertions were hit in the load test. At the moment I have to sift through the assertion log to figure out how many of each assertion were encountered.
4. I am seeing some wierd behavior with thread strategy. I will write an entry in the support section for this.