#help
Title
# help
j
Jens Don
10/11/2023, 8:47 AMI’m using wiremock for performance testing and I see a degradation in the wiremock performance. I’m using the standalone version with those parameters:
java -jar wiremock-standalone-3.2.0.jar --no-request-journal --disable-request-logging --async-response-enabled=true --container-threads=100
Any recommendations for optimalisation?
o
Oleg Nenashev
10/11/2023, 9:07 AMOne would need to profile to say for sure what causes the degradation. 100 threads seems to be too much for the async responses
j
Jens Don
10/11/2023, 9:53 AMDecreasing the threads to 50 make no difference. What is the best way to profile wiremock?
o
Oleg Nenashev
10/11/2023, 9:54 AMJFR on Java 17, Async profiler on 11 or 17
But you can start from simpler tools just to capture what gets saturated.
j
Jens Don
10/11/2023, 10:32 AMI’m having a JFR file now, let’s see if I can find anything useful
o
Oleg Nenashev
10/11/2023, 10:37 AMMemory and blocked threads are the first things to check
j
Jens Don
10/11/2023, 10:40 AMIs see a couple of blocked threads with the function equalToXmlPatterns. No memory issues found…
Issue fixed, changing the selectors to regex instead of xpath and equalToXml 👍🏼
o
Oleg Nenashev
10/12/2023, 9:10 AMWell, equalToXml is likely to be heavy. How big the XMLs are?
4 Views