Repository navigation
Conversation
Memory Profile ReportSummary
Iteration Details
Top Memory Allocations (by location)
Generated by Memory Profile workflow • Commit: bc0d33b |
Danger ReportNo issues found. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
grape-oas profiles memory use during OAS generation, but it has no repeatable way to measure generation time as an API's route count grows. This makes performance work harder to evaluate across OAS dialects.
Fix
Add a manually invoked
benchmark:generationRake task inspired by Grape'scompile_many_routes.rb. It builds synthetic APIs with 100, 500, and 1,000 routes, warms up each exporter, verifies the generated path count, and reports median generation time for OAS 2.0, 3.0, and 3.1.Route counts and iteration count can be overridden with environment variables. The benchmark uses Ruby's monotonic clock, so it adds no dependency. It is not connected to CI or release tasks.
Example
Output is tab-separated for easy comparison:
Schema before / after
No change to emitted output. This PR adds a standalone benchmark that calls the existing
GrapeOAS.generateAPI; library generation code is unchanged.Backward compatibility
🤖