Jackie chen
04/13/2023, 6:41 AMOleg Nenashev
04/13/2023, 8:33 AMJackie chen
04/16/2023, 12:05 PMOleg Nenashev
04/16/2023, 12:11 PMJackie chen
04/16/2023, 12:16 PMOleg Nenashev
04/16/2023, 12:28 PMJackie chen
04/16/2023, 12:57 PMOleg Nenashev
04/16/2023, 1:10 PMJackie chen
04/16/2023, 1:37 PMOleg Nenashev
04/16/2023, 6:11 PMJackie chen
04/17/2023, 1:25 AMOleg Nenashev
04/17/2023, 9:08 AMJackie chen
04/17/2023, 9:16 AMOleg Nenashev
04/17/2023, 9:20 AMTom
04/17/2023, 10:10 AMequalToXml
and equalToJson
tend to be the most demanding when the request bodies have large numbers of nodes. Record and playback of e.g. SOAP APIs tends to produce this outcome as it’s very easy to generate lots of stubs with big expected XML request bodies.Jackie chen
04/17/2023, 10:52 AMOleg Nenashev
04/17/2023, 10:55 AMTom
04/17/2023, 10:57 AMmatchesXPath
instead, assuming you can pick one or two elements in the XML body that uniquely identify the request.Jackie chen
04/17/2023, 11:16 AMHow large are your responses?
response size is ~320 KB, request size is ~1.1 KB with response content-encoding: gzipOleg Nenashev
04/17/2023, 11:24 AMTom
04/17/2023, 1:11 PMJackie chen
04/17/2023, 2:33 PMI think it should not matter since the actually invoked response is a JSON one.
you’re right, i only call the same equalToJson one scenario only but i see hotspots in EqualToXml (TransformerFactoryImpl) classes as per attached.