Take some commits of the TypeScript compiler, and figure out their relative performances

Перейти к файлу

Orta b4048157c7 Only use pure semver tags in latest		2020-12-08 17:47:32 +00:00
.github/workflows	It is now able to grab compile data for a single commit run	2020-12-08 17:44:10 +00:00
src	Only use pure semver tags in latest	2020-12-08 17:47:32 +00:00
.gitignore	It is now able to grab compile data for a single commit run	2020-12-08 17:44:10 +00:00
CODE_OF_CONDUCT.md	Initial CODE_OF_CONDUCT.md commit	2020-12-07 13:04:08 -08:00
LICENSE	Initial LICENSE commit	2020-12-07 13:04:10 -08:00
README.md	Only use pure semver tags in latest	2020-12-08 17:47:32 +00:00
SECURITY.md	Initial SECURITY.md commit	2020-12-07 13:04:13 -08:00
SUPPORT.md	Initial SUPPORT.md commit	2020-12-07 13:04:15 -08:00
package.json	It is now able to grab compile data for a single commit run	2020-12-08 17:44:10 +00:00
yarn.lock	It is now able to grab compile data for a single commit run	2020-12-08 17:44:10 +00:00

README.md

Generate stats on perf in a per-commit basis automatically

This has two current approaches in mind:

1. Use a single GitHub Action workflow to measure perf. We're looking for relative perf, so maybe that one computer is enough.
1. Use a GitHub Action to start up a beefy azure VM instance which runs this instead.

We'll try the first, and if that's not good enough, we'll try te second.

To run locally, using Node 13+, first clone:

git clone https://github.com/microsoft/TypeScript-Release-Deploy-Perf-Info
cd TypeScript-Release-Deploy-Perf-Info
yarn install

The use any of:

# Compare between two known refs
node src/diff.mjs run f646ec87fc master

# Compare current head to the latest release
node src/diff.mjs head

# Compare between the last two stable releases
node src/diff.mjs latest

The scripting is all done in NodeJS via ShellJs which allows for it to run in Windows and UNIX.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.