Add Standard (cross-sdk) Benchmarks

[alextwoods]

Add Standard (cross-sdk) Benchmarks

Motivation and Context

Add standard (cross-SDK) benchmarks for endpoint resolution and SERDE (marshalling/unmarshalling).

Modifications

Adds a new sdk-standard-benchmarks module with the standard (performance part-2) benchmarks for endpoint resolution and serde.

The SERDE tests are based on the standard performance test models and use our existing protocol test loader to load the c2j protocol tests defined on each of the protocol models.

Testing

Run all benchmarks

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[alextwoods]

This is a limitation of JMH - we can't dynamically load the json set of test cases and define a JMH parameter for it. @param values must be constant expressions at compile-time because of how JMH handles the lifecycle of a benchmark. To get the best measurements JMH is a generator that during build generates raw classes/methods for all of these.

[alextwoods]

The JsonRpc SERDE tests include tests marked for other protocols because the model contains operations from the cloudwatch model like GetMetricData - see test/sdk-standard-benchmarks/src/main/resources/serde-tests/json-rpc-1-0/input/json_1_0.json - it includes this full set of tests. They can be used to compare performance across protocols for comparable operations - useful when evaluating protocol migrations for services.

[RanVaknin]

Oh wow I was wondering about this. Very clever 👍