Skip to content

feat: add Octane benchmark - #36

Merged
lissy93 merged 1 commit into
lissy93:mainfrom
zhsama:feat/octane-benchmark
Aug 26, 2026
Merged

feat: add Octane benchmark#36
lissy93 merged 1 commit into
lissy93:mainfrom
zhsama:feat/octane-benchmark

Conversation

@zhsama

@zhsama zhsama commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add a standalone Octane implementation of the Weather Front benchmark.
  • Use Octane 0.1.34 with its official Vite plugin and compiled TSX components.
  • Register Octane development, build, lint, test, documentation, and benchmark configuration.

Why

Octane compiles React-style components into direct DOM updates without a virtual DOM. This implementation makes its production output and source characteristics comparable with the other framework variants.

Impact

The existing framework implementations remain unchanged. Contributors can run the new app through the generated octane root commands.

Validation

  • npm run build:octane
  • npm run lint:octane
  • npx playwright test --config=tests/config/playwright-octane.config.js --reporter=dot — 22 passed
  • python scripts/verify/validate_schemas.py
  • Source-analysis, bundle-size, and three-run build-time benchmark checks passed locally

@2u841r

2u841r commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

still draft?

@zhsama
zhsama marked this pull request as ready for review August 26, 2026 08:26
@zhsama

zhsama commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

Sry, forgot to convert it from draft. Ready for review now.

@lissy93 lissy93 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you @zhsama

@lissy93
lissy93 merged commit c82978a into lissy93:main Aug 26, 2026
63 of 65 checks passed
@lissy93

lissy93 commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Ah, the GitHub Actions workflows are failing which is why it's not live just yet.
But this isn't from this PR, seems that GitHub is just trying to keep to it's 20% downtime target 😅️

I'll come back in a couple hours and manually re-trigger them. I did test everything locally, so it should work 🤞️

image image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants