Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Repo: add tooling to performance test the tooling #6218

Open
Labels
performanceIssues regarding performancerepo maintenancethings to do with maintenance of the repo, and not with code/docsteam assignedA member of the typescript-eslint team should work on this.testsanything to do with testing
@bradzacher

Description

@bradzacher

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:

  1. total runtime
  2. peak memory usage

There's a few ideas we could use as tests:

  1. parse all fixtures to test TS parse + conversion runtime
  2. lint our codebase to test type-aware performance
  3. 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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    performanceIssues regarding performancerepo maintenancethings to do with maintenance of the repo, and not with code/docsteam assignedA member of the typescript-eslint team should work on this.testsanything to do with testing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp