aws-amplify / aws-amplify/amplify-hosting
Cold Start Issue in NextJS application
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [x] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [x] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [x] I have removed any sensitive information from my code snippets and submission.
### Amplify Hosting feature
Deployments, Frontend builds
### Is your feature request related to a problem? Please describe:
Hello Community,
Lot of users in amplify are facing the issue in which the website takes more than 3-4 seconds to load because of the cold start, It makes UI experience of the application bad, some users might drop of the website because of the cold start.
### Describe how you'd like this feature to work
I request you to improve the coldstart of the website which typically takes 3-4 seconds and make the UI experience of the Amplify better.
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing the Amplify Hosting deployment and frontend-build paths and reproduce the reported Next.js cold start; define a measurable startup target and validate it against a representative deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, next.js
- Domain
- cloud, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100