Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with inconsistent performance #39

Closed
mike183 opened this issue Jul 22, 2022 · 4 comments
Closed

Problems with inconsistent performance #39

mike183 opened this issue Jul 22, 2022 · 4 comments

Comments

@mike183
Copy link

mike183 commented Jul 22, 2022

Hi, I've been experimenting with edge-runtime using Next 12.2's Edge Server-Rendering with Vercel and have been experiencing some performance issues.

The application itself is very simple, just outputting "Hello World" from the index page in Next.js (see code below)

// pages/index.js
export default function Home() {
  return (
    <>
      Hello World!
    </>
  )
}

When loading this page via Vercel, I'm seeing response times ranging from 200-400ms, which in itself seems to be slower than I would expect.

This level of performance is consistent unless I repeatedly refresh the page, at which point response times begin to drop to 50-70ms, although this is sporadic and not very consistent.

I'm curious to know whether there is a real issue somewhere or whether I'm just doing something wrong.

You can find the deployed example application here, https://my-app-mike183.vercel.app/

Happy to share any further debug information that you might need 🙂

@shuding
Copy link
Member

shuding commented Jul 26, 2022

Hi Michael!

Currently the performance hasn’t been optimized for Next's Edge SSR mode, and we are actively working on it. For reference, you can check out https://react-on-the-edge.vercel.app which has a more ideal performance that we can expect for Next's Edge SSR.

@mike183
Copy link
Author

mike183 commented Jul 26, 2022

Thanks for clarifying @shuding! Is there anywhere that we can follow the progress of the performance work?

@shuding
Copy link
Member

shuding commented Jul 26, 2022

We are doing improvements directly to the Next.js repository, e.g.: vercel/next.js#38570. But we don't have a specific thread to track it right now.

@mike183
Copy link
Author

mike183 commented Jul 26, 2022

Thanks @shuding! I’ll close this issue since it’s seems to be more of a Next.js problem than edge-runtime.

@mike183 mike183 closed this as completed Jul 26, 2022
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

No branches or pull requests

2 participants