improve the perf
- Dominant language
- C#
- Stars
- 290
- Forks
- 50
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 5
Description
For some big swagger, it seems too slow, the problem is that the tool does the below thing during its run
1 use autorest(v2) to transform the swagger and get a resolved swaggger and source mapping file
2 transform the swagger allOf and path level parameter to make it fit the modeling which is defined in C#
when we consider improving the perf, we can focus on above points
Contributor guide
Research direction
Start by profiling the two stages named in the issue: AutoRest v2 resolution with source mapping, and the transformations for Swagger allOf and path-level parameters. Compare runs on a large Swagger document; done should mean measurable performance improvement, but the issue does not specify files, tests, or a target benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, openapi
- Domain
- cli, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100