[Res] SoapUI Memory Limits?

Hi,

I don't believe there are any memory limits for 64 bit SoapUI Pro in the application itself. Memory allocation depends on the JVM. If you set the max Heap to be greater than 2 GB doesn't mean the JVM is going to allocate more than 2 GB from the start. That's the max amount the JVM is going to use. If needed the JVM can allocate more than 2 GB if your JVM Heap Size is greater than 2 GB.




Regards,
Marcus
SmartBear Support

Hi Marcus,

Thanks for your response. I'm trying to run a load test that will require all of the memory resources on my machine. My thought was that it would be possible to allocate all the available system memory to one SoapUI instance since the system is 64-bit. However so far I am not sure one SoapUI can use all of the available memory and I've observed that performance is better when testing with multiple SoapUI instances.

Here's what my startup params look like:
[oracle@tgen01 bin]$ ps aux | grep soap
oracle 18483 0.0 0.0 106152 1316 pts/0 S+ 19:15 0:00 /bin/sh ./soapui-pro.sh
oracle 18487 37.9 4.3 7406504 705188 pts/0 Sl+ 19:15 0:23 /home/oracle/SmartBear/SoapUI-Pro-4.6.4/jre/bin/java -Xms3072m -Xmx3072m -XX:PermSize=512m -Dsoapui.properties=soapui.properties -Dgroovy.source.encoding=iso-8859-1 -Dsoapui.home=/home/oracle/SmartBear/SoapUI-Pro-4.6.4/bin -splash:soapui-pro-splash.png -Dsoapui.ext.libraries=/home/oracle/SmartBear/SoapUI-Pro-4.6.4/bin/ext -Dsoapui.ext.listeners=/home/oracle/SmartBear/SoapUI-Pro-4.6.4/bin/listeners -Dsoapui.ext.actions=/home/oracle/SmartBear/SoapUI-Pro-4.6.4/bin/actions -Djava.library.path=/home/oracle/SmartBear/SoapUI-Pro-4.6.4/bin -Dwsi.dir=/home/oracle/SmartBear/SoapUI-Pro-4.6.4/wsi-test-tools -cp /home/oracle/SmartBear/SoapUI-Pro-4.6.4/bin/soapui-pro-4.6.4.jar:/home/oracle/SmartBear/SoapUI-Pro-4.6.4/lib/* com.eviware.soapui.SoapUIPro

I've tried setting the initial heap to 3GB (with Xms) but the memory log tab in SoapUI only shows 2GB allocated. I ran a load test increasing the thread count to 750. As the number of threads increased it looked like there was more garbage collection happening but the max allocated memory reported in SoapUI never increased beyond the 2GB. Any pointers would be appreciated. Thank you!

Hi,

I'm going to ask development to take a further look at this. It's possible there maybe memory restrictions for SoapUI. The thread count of 750 threads sounds a bit high to me for one JVM. Also, you mention SoapUI instances, are you using a load test tool such as LoadUI in this load test?





Regards,
Marcus
SmartBear Support

Thanks Marcus I appreciate that. We are currently not using LoadUI- just multiple SoapUI instances for the testing. We just migrated to a new 64-bit server coming from a 32-bit machine. To make use of all the server's memory in the 32-bit server we were forced to run the test over multiple SoapUI instances due to the 4GB memory limit per process. I was hoping this could be avoided on a 64-bit system!

Hi,

We have tried to the same thing on linux 64 bit machine and saw the same behavior in memory log that, it is restricted to 2GB. But when we tried to get the actual memory usage with a groovy script it showed the correct higher number. So, we think the memory log number is not correct when it crosses 2GB.

We have a ticket reported for this issue SOAP-1574 in our internal bug tracking system.

Thanks,
Shadid
SmartBear Sweden.

Thanks Shadid. I also saw in my load test that the memory usage of the process grew (more than 8GB actually) but I'm still concerned the java heap may be limited to 2GB. I think the extra memory usage may have been due to the extra thread stacks created in my test.

Hi,

Now there is a fix available on the maintenance build. You can try it out to see if the memory log shows correct reading.

Regards,
Shadid
SmartBear Sweden

Thank you Shadid. It's definitely closer. The allocated memory is reported correctly now but the graph still isn't working and the used memory calculation seems to wrap around to negative numbers after growing past 2GB... May be easier to see from the screenshots below.

http://i.imgur.com/drc3UAf.jpg
http://i.imgur.com/d7VdbB4.jpg

Hi,

Yeah we saw that. Thanks! We will put a fix for that soon.

Regards,
Shadid
SmartBear Sweden

Hi,

Maintenance build has a new patch now. Try it out when you have time and see if it resolves the issue.

Regards,
Shadid
SmartBear Sweden