Thanks J_NeSmith
Please find my comments inline. However we have ran another test after sometime and the results were as expected.
What indicators did you use to determine the capacity of 100 was a proper setting?
<Nikhil> Earlier the Capacity was set to 1, Default one. We thought this was the reason so changed it to 100 thinking that is the maximum transactions that can come to virtual service in a shot.
How many other Virtual Services are active during this load test? If any were running, do these services have a high capacity setting?
<Nikhil>There are around 60 virtual services are running but those are of completley differnt virtual services, They do not have any interaction with this virtual service.
Within Portal, what was the highest TPS rate achieved by the service during the load test?
<Nikhil> For other services - the maximum TPS was 150
What is the response SLA (Think Time) set to?
<Nikhil> The SLA is 3000 milli seconds - which is given in the Virtual Service Image
Can you share information about the 'internal server errors' you refer to?
- Perhaps, some log file excerpts are available.
<Nikhil>
Unexpected Exception occured
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.7.0_55]
Can you provide some additional information about the transactions in the load test ( avg. payload size, # TPS or virtual users targeted, VS protocol, etc.)
<Nikhil> In 10 mins of load test - there were 6600 passed transactions and roughly about 360 internal server error transactions.
The maximum TPS for this service is 14
Can you offer information about the VSM/VSI under test
- Number operations / responses
- <Nikhil>There are completley 79 differernt responses configured
- Any operations with a high number of incoming request arguments
- <Nikhil>Not exactly
- Does the virtual service under test have customizations (added steps, custom dphs, database I/O, Match Scripts, etc.)
<Nikhil>No, there is no extra customizations done to this service.
Can you provide some high level server configuration information?
- OS, # CPUs, # Cores per CPU <== CPUs and Cores affect the maximum capacity setting
- What other services are running on the server where the VSE service is running
<Nikhil>There are other services running but no body was doing any testing on those services
- What is the heap allocation for the VSE (vmoptions)
- <Nikhil>6gb
- Did you make any changes to the OOTB GC (vmoptions)
<Nikhil>No
- Yes for the Other performance test, that was resulting us in higher CPU Utilization.