Azure
/
azure-sdk-for-js
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
azure-sdk-for-js/sdk/core/perf-tests/core-rest-pipeline
История
Jeremy Meng 59bb0809ba [EngSys] use vendored version of `mkdirp` and `rimraf` from dev-tool 
also remove dependency on `@microsoft/api-extractor` as we already move to
`dev-tool run extract-api` which calls api-extractor Api instead.

***NO_CI***
 		2024-10-23 17:53:07 +00:00
..
test [EngSys] standardize OSS copyright header 2024-08-27 13:01:38 -07:00
CHANGELOG.md [core-rest-pipeline] Merged bearerTokenChallengeAuthenticationPolicy into bearerTokenAuthenticationPolicy (#15415) 2021-06-01 14:51:43 -04:00
README.md [engsys] remove `node-fetch` perf tests (#28152) 2024-01-05 14:21:01 -08:00
package.json [EngSys] use vendored version of `mkdirp` and `rimraf` from dev-tool 2024-10-23 17:53:07 +00:00
sample.env [core-rest-pipeline] WWW-Authenticate challenge perf-stress test (#14659) 2021-05-03 21:58:22 +00:00
tsconfig.json [EngSys] remove tsconfig.package.json 2024-07-16 13:27:25 +00:00

README.md

Guide

  1. Build the core-rest-pipeline perf tests package rush build -t perf-core-rest-pipeline.
  2. Copy the sample.env file and name it as .env.
  3. Populate the .env file with your Azure Credentials.
  4. Refer to the rate limits and then run the tests as follows:
  • bearerTokenAuthenticationPolicy test for the challengeCallbacks, for simple WWW-Authenticate challenges.
    • npm run perf-test:node -- BearerTokenAuthenticationPolicyChallengeTest --warmup 1 --iterations 1 --parallel 5
  • Comparing various HTTP clients...
    • npm run perf-test:node -- UndiciRequestTest --warmup 1 --iterations 1 --parallel 5 [ 19,733.93 ops/sec ]
    • npm run perf-test:node -- CoreRestPipelineTest --warmup 1 --iterations 1 --parallel 5 [ 17,519.69 ops/sec]
    • npm run perf-test:node -- HttpRequestTest --warmup 1 --iterations 1 --parallel 5 [ 19,632.64 ops/sec] [ -- number ops/sec -- ] are from a codespaces instance