You are running a performance VSE and have initialized the lisa.vse.performance.enable property, correct?
Assuming the answer to above is yes, continue. If not, ensure you are licensed and turn on performance.
I know this sounds a bit crazy, but what technique did you use to identify that the response time in and out of the VSE server is 5 seconds? Do you have any probes on the server or tools such as Wireshark, tcpdump, etc to help you understand the traffic on / off the actual NIC.
It will be difficult to explain in this forum why you see the behavior you see without more information about the type of service and environment you are running. Can you please give us some additional background:
- Which version of DevTest
- What type of service are you testing (HTTP, JMS/MQ, Java, CICS, etc)
- What is the avg size of the request & response payloads?
- Have you customized the VSM, if so describe the customizations (filters, xpath, custom script, file i/o)?
- Is SSL involved
- Is any Live Invocation occurring during the performance test
- Are you using the OOTB Derby DB or a recommended Enterprise DBMS
- How many other services are active in the VSE during this test? How many services are participating in this test?
- Is heavy logging into the VSE.log occurring (look at lisatmp for vse.log, vse.log1, vse.log2). Excessive logging or file I/O can slow performance.
- How many TPS are you sending to the service / what is the target TPS rate you are seeking
- At what point during the test do you see the response times at 5 seconds?
- When the test executes, what does the Portal Console (Monitor, VSE, your service) show as the TPS rate, # transactions, etc.
- What method did you use to determine that a Capacity of 5 was sufficient for the load test?
- What OS, CPU Cores, and RAM
- What other Services are active on the OS (Registry, Coord, Portal, Sim, 3rd party services)
- During the test what amount of CPU is the VSE Service consuming
- What does OS Performance console show while the test is running (OS, CPU, Network, etc)
- Are you using default JVM memory on the VSE or have you assigned an amount of memory