[DO NOT MERGE] CBOR Performance Testing #3173
Conversation
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
|
You have made a change to core without a corresponding change to the CHANGELOG.md. This change will not result in a new version and will not published unless an entry is added to CHANGELOG.md. |
You could probably remove the CI task that checks for the changelog entry in this branch since we never intend to merge it. Or event invert the logic of it - comment if we DO have a changelog (since not having a changelog for these changes protects us from accidently releasing them if we did accidentally merge this branch). |
These changes are intended to stay in the cbor-perf-testing branch and NOT to be merged to version-3. This PR was opened to facilitate review and discussion.
Run tests with
zsh perf-testing/run-perf-tests.sh <iteration_number>. The actual test with 500 iterations can be executed withzsh perf-testing/run-perf-tests.sh 500.The test output for each suite (Local only, Secrets Manager, CloudWatch) can be found in their respective directories under perf-testing/test-output. The data.txt file contains the properly formatted results and the raw.txt files contains the measured data points for each test case. The combined outputs are under perf-testing/test-output/combined.