Conversation
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.
The baseline benchmark renders the same 1000-row UUID table as the framework apps do, but using plain Node.js template literals without a framework. It calls testData() and builds the HTML string on each request, giving a raw ceiling for SSR throughput that shows exactly how much overhead each meta-framework adds. Not sure if this is the best way, should it be compared to more SSG? Not sure anyway this will do for now
Checklist
starter-*package, ensure that the deps, and file content matches the output of the metaframeworks recommended starter/default projectOverview:
Yes they say
0will update when tests run on mergeDetails: