Repository navigation
Show the preliminary deploy benchmarks on the website [skip ci] - #321
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
…ip ci] Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.
Adds a
/benchmarkspage and one benchmark result under homepage sections 02 and 03. All numbers are published medians from stacktape/deploy-benchmarks (22 and 23 October 2026), labelled as preliminary.What changed
/benchmarksuses the homepage's README layout: the repo header, one document and an "About these results" column. The document holds one chart with five tabs: Packaging, Lambda deploy (handler or shared-code change), Container deploy, Git push and Image size. Each tab draws horizontal bars on one scale. Stacktape is teal, other tools are grey, values sit at the bar tips and the fastest tool in each group is marked. Tabs use the shared@stacktape/ui-reactTabs(arrow keys,role="tablist"). The island is server-rendered, so the first tab shows without JavaScript.#git-pushand the other tab IDs select a tab.apps/website/src/data/deploy-benchmarks.jsonstores the source URL and the run dates. Each value records its median, range, run count, date and the results file it came from./#designsand/#get-started, so they work from/benchmarkstoo.Honesty choices
results/2026-10-23/console-app-130. The benchmark README now presents that fix as part of the current product. Stacktape still loses the Python push to Heroku (23.9 s against 20.0 s), and the note under the chart says so. The note also gives the smaller run counts (5 or 6) and the earlier pre-fix times (58.4 and 80.9 s).codeSwap: true), and they give the image-deploy times from 17 October, which lose.Checks
pnpm --filter @stacktape/website typecheckandbuildpass./and/benchmarksreturn 200 inastro preview.scrollWidthequals the viewport width.🤖 Generated with Claude Code