This message was deleted.
# help
s
This message was deleted.
o
One would need to profile to say for sure what causes the degradation. 100 threads seems to be too much for the async responses
j
Decreasing the threads to 50 make no difference. What is the best way to profile wiremock?
o
JFR on Java 17, Async profiler on 11 or 17
But you can start from simpler tools just to capture what gets saturated.
j
I’m having a JFR file now, let’s see if I can find anything useful
o
Memory and blocked threads are the first things to check
j
Is 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
Well, equalToXml is likely to be heavy. How big the XMLs are?