denoland / denoland/deploy_feedback
Aot builds of Fresh on Deploy are significantly slower than Jit
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
[Continuing from Discord](https://discord.com/channels/684898665143206084/991511118524715139/1220294825467842570)
When deploying a project on Deno Deploy that uses Fresh's aot builds (via github actions) the start times are much slower than projects using deploy's automatic deployment feature.
Fresh projects using aot:
Fresh projects not using aot:
When one of the non aot projects was updated to the latest build of fresh:
All aot and the last non aot are using the latest version of fresh
Contributor guide
No contributing guide indexed for this repository
Research direction
The report provides deployment screenshots and mentions Fresh AOT builds, Deno Deploy automatic deployment, and GitHub Actions, but no repository files or tests. Reproduce the two deployment paths and compare startup times; done means identifying the cause of the slower AOT starts and verifying comparable results after the issue is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- cloud, devops, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100