Skip to content

Commit

Permalink
updated readme with summary
Browse files Browse the repository at this point in the history
  • Loading branch information
William Armiros committed Sep 3, 2020
1 parent 3977ed7 commit 6a2d4d0
Showing 1 changed file with 13 additions and 1 deletion.
14 changes: 13 additions & 1 deletion aws-xray-agent-benchmark/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,19 @@ The results will be output into the `build/reports/jmh` directory after the test

## Benchmark Results

TODO: summary of performance of the three modes.
The below table summarizes the **approximate** latency added using both manual X-Ray SDK and automatic
X-Ray agent-based instrumentation for different activities in microseconds. These numbers should not be
considered precisely accurate in all applications, they are just to give an idea of added latency.
Overall, you can see that in a typical application the SDK or the agent would not add more than a single-digit
amount of milliseconds to a request.

| | SDK Instrumentation | Auto Instrumentation |
|--------------------------|---------------------|----------------------|
| Service incoming request | +100 us | +110 us |
| SQL Query | +70 us | +60 us |
| AWS SDK V1 Request | +30 us | +60 us |
| AWS SDK V2 Request | +30 us | +90 us |
| Apache HTTP Request | +20 us | +40 us |

You can also take a look the [results directory](https://github.com/aws/aws-xray-java-agent/tree/master/aws-xray-agent-benchmark/results)
for detailed benchmarking data from previous versions of the agent. Since we use an arbitrary delay to simulate the effect
Expand Down

0 comments on commit 6a2d4d0

Please sign in to comment.