Forum Discussion
jens
16 years agoNew Contributor
Hi Ole,
- the Version is 3.5 (free right now, pro soon).
- The dispatcher choosen right now is just sequence and there exists just one response. We are planning to complicate things later on with scripting, though.
- There are no scripts involved in the mock functionality (again, planning to).
To illustrate the situation, please find a screenshot attached. The difference in response time between the services with just a few operations and those with more is staggering. This test run had the mock service as a direct communication partner configured. Our intermediary did not take part.
As you can see, the response times inside the poorly performing mock service increases along the operators. Hence my guess concerning the thread pool.
Best regards,
Jens
- the Version is 3.5 (free right now, pro soon).
- The dispatcher choosen right now is just sequence and there exists just one response. We are planning to complicate things later on with scripting, though.
- There are no scripts involved in the mock functionality (again, planning to).
To illustrate the situation, please find a screenshot attached. The difference in response time between the services with just a few operations and those with more is staggering. This test run had the mock service as a direct communication partner configured. Our intermediary did not take part.
As you can see, the response times inside the poorly performing mock service increases along the operators. Hence my guess concerning the thread pool.
Best regards,
Jens