We are currently in the process of developing a webService on webMethods IS which will be used by a lot of client (300 + Concurrent connections). I have created the service and tried heard to make it as optimal as possible. Create a WSDL and created a .Net client to use the WSDL. Tried with 1 client invocation the process time (200 ms) is exception and well below the SLA (2 secs). But when I put this through a load generator (JMeter) with 50 threads it started chocking, the response time climbed up to (15 secs). the response time graph is directly proportional to the number of concurrent threads. When I turned off the session logging the perfomance was much better (2.5 secs) but still not meeting my SLA. We are planning to cluster the IS instances with a hardware load balancer but I want to know if there is any thing else I could do better to improve the performance. Especially I want to see how we can use GLUE or Service Net in this kind of senarios.
Any help or a direction is much appreciated.