You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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)
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 🙂
The text was updated successfully, but these errors were encountered: