Thank you Jamesdunn and Danny,
Added my comments. Could you please check and advice.
- You show the response time graph, What does the number of transactions per second graph show aroound those period? Just your average 60 tps or does it also show spikes?
Average transactions per second graph is steady during the spike time.
- JVM garbage collection is something that could cause JVM to temporarily do much less work/processing and subsequently let the average response time spike. You mention your system has 64GB RAM but how much memory has been configured for the VSE process?
8 GB Memory is configured for VSE process. And i am not sure how to check is there any JVM garbage collection activity occurred during that time.
- If your average transactions per second graph is steady, and the JVM garbage collection is not the cause, then you would have to know what is happening to your system resources at those particular periods of time. Is some other process kciking in and consuming CPU and/or Memory?
I have consulted Admin team and got confirmation that no other process kicked in during that time.
I have seen this kind of behaviour very frequently during performance test runs. I could not see any details in logs also.
I have also experienced similar behaviour during performance tests- Do you have anything special in your virtual service like match scripts or custom coding?
This particular service doesn't contain any thing like match script or Custom Coding. Can you please let me know, if virtual service contains any Match Script or Custom Coding, will it affect the performance.
Than you
Rajasekhar