Skip to content

⚡️ Perf: Run performance comparison for ts.JSDocParsingMode.ParseForTypeInfo #7906

Open
@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Suggestion

Splitting out of https://devblogs.microsoft.com/typescript/announcing-typescript-5-3-beta/#optimizations-by-skipping-jsdoc-parsing -> #7821 (comment): we'd like to use the new JSDocParsingMode flag. But how beneficial is it, exactly? Let's run some kind of performance comparison to see.

From @bradzacher:

My original perf profiling way back when showed a decent chunk of time spent but things may have changed since then.
Note: the more important time would be the non-type-aware lint time as type info would dwarf any savings we get.

#7870 is an example of me setting up a Hyperfine comparison.

Metadata

Metadata

Assignees

No one assigned

    Labels

    performanceIssues regarding performanceteam assignedA member of the typescript-eslint team should work on this.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions