Skip to content

High TTFB for NextJs application #3357

Closed
Closed
High TTFB for NextJs application#3357
Assignees
Jay2113
Labels
archivedThis issue has been locked.bugSomething isn't workingcomputeinvestigating

Description

@Akhilesh-aarzoo
Akhilesh-aarzoo
opened on Mar 8, 2023

Before opening, please confirm:

  • I have checked to see if my question is addressed in the FAQ.
  • I have searched for duplicate or closed issues.
  • I have read the guide for submitting bug reports.
  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.

App Id

dyyv7k61mxhcc

AWS Region

us-east-1

Amplify Hosting feature

Not Applicable

Describe the bug

We have a NextJs application hosted on Amplify. We are seeing high TTFB for our application in production. We are getting this problem without any changes at our end. This is happening since 2:30 AM UTC today.

Expected behavior

TTFB should not take so long. It should be back to normal.

Reproduction steps

  1. Deploy a NextJs app on Amplify on us-east-1
  2. Use the hosted application URL on browser and check the Network tab

Build Settings

version: 1
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'

Log output

Details 
# Put your logs below this line

Additional information

No response

Activity

  1. Akhilesh-aarzoo
    added
    bugSomething isn't working
    pending-triage
    on Mar 8, 2023

  2. rebeccatay92 commented on Mar 8, 2023

    @rebeccatay92
    rebeccatay92
    on Mar 8, 2023

    Can confirm this is happening on our Amplify applications as well, starting this morning. Vanilla React is ok but NextJS applications hv high TTFB (sometimes > 20s)
    App Id d1bzv6vd8539jw
    AWS Region us-east-1

  3. Jay2113
    added
    investigating
    and removed
    pending-triage
    on Mar 8, 2023
  4. Jay2113
    self-assigned this
    on Mar 8, 2023
  5. Jay2113
    added
    s1
    compute
    on Mar 8, 2023

  7. ArianHamdi commented on Mar 8, 2023

    @ArianHamdi
    ArianHamdi
    on Mar 8, 2023

    Same here also.

  8. Akhilesh-aarzoo commented on Mar 9, 2023

    @Akhilesh-aarzoo
    Akhilesh-aarzoo
    on Mar 9, 2023
    Author

    @hloriana - Why are we seeing high TTFB all of a sudden? We didn't make any code changes/deployments. Did something change in AWS Amplify yesterday?

  9. ferdingler commented on Mar 9, 2023

    @ferdingler
    ferdingler
    on Mar 9, 2023
    Contributor

    We are looking into this

  10. timedtext commented on Mar 11, 2023

    @timedtext
    timedtext
    on Mar 11, 2023

    @ferdingler Please take a look at my discovery. #3359 (comment)

  11. jbreemhaar commented on Mar 14, 2023

    @jbreemhaar
    jbreemhaar
    on Mar 14, 2023

    @ferdingler Please have a look at #3211.
    Issues for me started since migrating WEB_COMPUTE two days ago.
    image

  12. ArianHamdi commented on Mar 14, 2023

    @ArianHamdi
    ArianHamdi
    on Mar 14, 2023

    @ferdingler Please have a look at #3211. Issues for me started since migrating WEB_COMPUTE two days ago. image

    High TTFB in 03/08 & 03/09
    image

  13. ghost removed
    s1
    on Mar 17, 2023

  14. Akhilesh-aarzoo commented on Mar 22, 2023

    @Akhilesh-aarzoo
    Akhilesh-aarzoo
    on Mar 22, 2023
    Author

    It's been more than 2 weeks and there is no update here.
    This is the support we get for production issues (production system going down)? Or is this the AWS way to make us subscribe to their Support plan?

  15. isaac1400 commented on Mar 24, 2023

    @isaac1400
    isaac1400
    on Mar 24, 2023

    In my company we are also experiencing long load times for our nextjs apps.

  16. jbreemhaar commented on Mar 28, 2023

    @jbreemhaar
    jbreemhaar
    on Mar 28, 2023

    I've (temporarily) fixed this by setting up a Cloudwatch Synthetic Canary, which fetches the url of my amplify app(s) every 5 minutes and so keeps the Lambdas warm.

    Cloudwatch > Application monitoring > Synthetics Canaries where you can pick the Heartbeat monitoring blueprint.

  17. soplan commented on Mar 28, 2023

    @soplan
    soplan
    on Mar 28, 2023

    I've (temporarily) fixed this by setting up a Cloudwatch Synthetic Canary, which fetches the url of my amplify app(s) every 5 minutes and so keeps the Lambdas warm.

    Cloudwatch > Application monitoring > Synthetics Canaries where you can pick the Heartbeat monitoring blueprint.

    This will only solve the issue if you do not have a high traffic website. If 2 people simultaneously access your website, one of them would still experience a cold start

  18. benjibenoit commented on Apr 17, 2023

    @benjibenoit
    benjibenoit
    on Apr 17, 2023

    Same problem here ! ~5s TTFB

  19. abepuentes commented on Apr 21, 2023

    @abepuentes
    abepuentes
    on Apr 21, 2023

    Here is around 10s TTFB

  20. Jay2113 commented on May 3, 2023

    @Jay2113
    Jay2113
    on May 3, 2023
    Contributor

    Hey everyone 👋 , thank you for your continued patience.

    We are actively investigating and are working on narrowing down the root cause of the elevated latencies (high TTFB) with Compute apps. Please rest assured that this is our highest priority and we will keep you posted with any updates.

    Apologies for the inconvenience caused due to this behavior with Compute apps.

  21. calavera commented on Jul 27, 2023

    @calavera
    calavera
    on Jul 27, 2023
    Contributor

    Hey everyone 👋

    We just released some changes to improve how long it takes to serve content from Next.js apps. These changes require a new deploy in your application to take effect. The expected outcome is that your sites should load quicker than before.

    If you have comments or questions don't hesitate to reach us via AWS support.

  22. calavera
    closed this as completedon Jul 27, 2023

  23. github-actions commented on Jul 27, 2023

    @github-actions
    github-actionsbot
    on Jul 27, 2023

    ⚠️COMMENT VISIBILITY WARNING⚠️

    Comments on closed issues are hard for our team to see.
    If you need more assistance, please open a new issue that references this one.

  24. github-actions commented on Jul 27, 2023

    @github-actions
    github-actionsbot
    on Jul 27, 2023

    This issue has been automatically locked.

  25. github-actions
    added
    archivedThis issue has been locked.
    on Jul 27, 2023
  26. github-actions
    locked and limited conversation to collaborators on Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

archivedThis issue has been locked.bugSomething isn't workingcomputeinvestigating

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions