|
In this example you will see two recordings from the same application. The application that has been recorded uses a common method for logging transactions, which causes many latencies due to Java synchronization. These latencies can be found in almost all threads in the recording that is named pricing-server-logging.xml.zip (Figure 16-18).
For the second recording the same application has been used, but the calls to the logging system has been removed, which causes a lot less latencies in the system. The second recording is named pricing-server-no-logging.xml.zip (Figure 16-19). You see the difference both in the color scheme and the Latency Timeline slide bar.
You can compare the two JRA recordings next to each other within the JRA Tool, which makes it easier to see what has happened with the changes in the application (see To compare and contrast JRA recordings for information on how to compare recordings).
|
|