Forum Discussion
SmartBear_Suppo
Alumni
14 years agoHi Victor!
I haven't done any benchmarks myself, but I would assume that running Mock Services in soapUI and loadUI (using the Mock Service Component) will give the same performance, since loadUI uses the actual soapUI engine for all soapUI related things (soapUI Runner and Mock Service Component). However, you will get better logging in soapUI.
If I had to pick between soapUI and Tomcat when it comes to speed, I would pick Tomcat. Not because it would execute the code any faster (it's still the same Java Bytecode), but the tuning options and response caching is probably better in Tomcat.
In the end, the only way to know for sure if your mocks is a bottleneck, is to load test them (and preferably also monitor your servers to see whether they hit a resource limit, using loadUI Pro).
Regards
Henrik
SmartBear Software
victor23 wrote: My question is: would running the mocks in loadUI, or exporting them as a war (and running on Tomcat), produce better performance under load (including many simultaneous requests) compared to running the mocks directly in soapUI?
I haven't done any benchmarks myself, but I would assume that running Mock Services in soapUI and loadUI (using the Mock Service Component) will give the same performance, since loadUI uses the actual soapUI engine for all soapUI related things (soapUI Runner and Mock Service Component). However, you will get better logging in soapUI.
If I had to pick between soapUI and Tomcat when it comes to speed, I would pick Tomcat. Not because it would execute the code any faster (it's still the same Java Bytecode), but the tuning options and response caching is probably better in Tomcat.
In the end, the only way to know for sure if your mocks is a bottleneck, is to load test them (and preferably also monitor your servers to see whether they hit a resource limit, using loadUI Pro).
Regards
Henrik
SmartBear Software