SV-VSEs showing different Response Times results compared to the baseline VSE

book

Article ID: 145502

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

I ran the traffic from JMETER scripts straight. to the Virtual Services on the same server.  For example, traffic was run from JMETER on the CIG4W1280 server to the Virtual Services on the CIG4W1280 server.  I repeated this process across the other 3 servers.   We have 4 Windows servers that are exactly the same build and we have 4 VSEs on each of the Servers.  I ran the same test across all 4 servers and I am seeing drastically different results from the 1 server compared to the other 3.  I made sure that I was the only one running traffic so I could get clean results.  As you can see from the results below there is something not right and I feel that we should be able to implement some optimizations to get better performance from the servers that are drastically worse as seen below.  need some help to troubleshoot why there is such a huge difference here.  I also made sure the the Virtual service settings were the same for the services I was testing on each VSE.  For example capacity and latency settings the same across the board.





 

Average
Response Times


Label


1280 Baseline


1281 Avg After Changes


1301 Avg After Changes


1302 Avg After Changes


getAccountGroupSummaryAssetClass


29


383


399


407


getAccountGroupSummaryAssetClassV2


32


381


411


404


getAcctDocReviewFlag


26


375


399


389


getAcctInfo


24


145


155





































































































































































 

Average
Response Times


Label


1280 Baseline


1281 Avg After Changes


1301 Avg After Changes


1302 Avg After Changes


getAccountGroupSummaryAssetClass


29


383


399


407


getAccountGroupSummaryAssetClassV2


32


381


411


404


getAcctDocReviewFlag


26


375


399


389


getAcctInfo


24


145


155


152


getAcctPrcsInfo


27


383


403


390


getAdvisorInfo


20


375


396


375


getAssetDetails


52


382


422


405


getCPFAEntitlement


24


379


403


390


getDisposedLots


92


417


482


473


getDrawDetails


18


27


26


31


getJournalAccountInfo


28


402


417


414


getMTAcctInfo


24


169


175


181


getPayDetails


25


165


135


156


getPositionsList


26


371


393


389


getTransactionHistory


77


414


461


454


getTransactionReportFilters


19


365


413


411


offerDecision


103


434


438


434


paymentSubmit


18


26


15


21


scheduleOneTimeJournal


22


3


3


3


scheduleOneTimeTransfer


22


129


154


136


scheduleRecurringTransfer


23


69


87


80


submitDrawDetails


25


124


134


130


transactionActivityDetails


23


157


151


146

Cause

Load balancer configuration

Environment

Release : 10.4

Component : SERVICE VIRTUALIZATION DOC

Resolution

Please work with the Load balancer configuration team to get this resolved.