Add perf tests for track 2 librareis

[jeremymeng]

Perf tests is one of the requirements for releasing a track 2 GA package. We should add perf tests for all our track 2 libraries and make it a item in the release checklist. The main goal is to cover our SDK code but you may want to consult the service team on the scenarios to target.

Wiki page on how to add perf tests: https://github.com/Azure/azure-sdk-for-js/wiki/Writing-Performance-Tests

There are several SDKs in this repo that have the perf test projects. Examples below

• https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/perf-tests/storage-blob
• https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/perf-tests/storage-blob-track-1
• https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/eventgrid/perf-tests/eventgrid
• https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/textanalytics/perf-tests/text-analytics

Packages:

• Anomaly Detector Add Anomaly Detector Performance Tests  #15514
• App Config
• Attestation [Attestation] Add perf tests #17839
• Communication Add Communication SDK Performance Tests #15517
  • Chat
  • Network Traversal
  • Phone Numbers
  • SMS
• Container Registry
• Cosmos DB [Cosmos] Add perf tests #17841
• Digital Twins Add Digital Twins Performance Tests #15515
• Event Grid
• Event Hubs
• Form Recognizer
• Identity
• Key Vault
  • Certificates
  • Keys
  • Secrets
  • Admin [KeyVault Admin] Add perf tests #17843
• Metrics Advisor
• Mixed Reality Authentication [Mixed Reality Auth] Add perf tests #17844
• Monitor OpenTelemetry Exporter
• Mixed Reality Remote Rendering [Mixed Reality Remote Rendering] Add perf tests #17845
• Schema Registry [Schema Registry] Add perf tests #16983
• Search Documents
• Service Bus
• Storage
  • Blob
  • Blob ChangeFeed [Storage ChangeFeed] Add perf tests #17847
  • File DataLake
  • File Share
  • Queue [Storage Queue] Add perf tests #17848
• Data Tables
• Text Analytics
• Web PubSub [Web PubSub] Add perf tests #17849

[github-actions]

Hi @jeremymeng, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.