-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Labels
performanceIssues regarding performanceIssues regarding performancerepo maintenancethings to do with maintenance of the repo, and not with code/docsthings to do with maintenance of the repo, and not with code/docsteam assignedA member of the typescript-eslint team should work on this.A member of the typescript-eslint team should work on this.testsanything to do with testinganything to do with testing
Description
Suggestion
We really should have tooling which lets us perf test our tooling.
Specifically we'd want to the test to monitor two main metrics:
- total runtime
- peak memory usage
There's a few ideas we could use as tests:
- parse all fixtures to test TS parse + conversion runtime
- lint our codebase to test type-aware performance
- lint some predefined set of OSS codebases at specific commits to validate real-world performance (type-aware and non-type-aware)
Maybe we don't need to do this on every PR - perhaps something we could trigger via a bot command (similar to what the TS team does in the TS repo).
JoshuaKGoldberg and rdsedmundo
Metadata
Metadata
Assignees
Labels
performanceIssues regarding performanceIssues regarding performancerepo maintenancethings to do with maintenance of the repo, and not with code/docsthings to do with maintenance of the repo, and not with code/docsteam assignedA member of the typescript-eslint team should work on this.A member of the typescript-eslint team should work on this.testsanything to do with testinganything to do with testing