-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
site: turn off edge serving for REPL #9136
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
Conversation
|
|
I still think we should give edge a chance. Set two regions close to the database and lets observe, I feel that alone will fix most issues. Edge is more resilient than serverless. With serverless, if one region goes down, it goes down for a long time until AWS fixes it. With edge, you got 500 once, and on second reload it'll switch to nearby region. How about trying for these regions: |
|
I'm in favor of trying this out, given how big the dip is and how reliable it was before. Let's test, measure and potentially tweak later. |
|
unsubscribe
…On Tue, Aug 22, 2023 at 2:52 PM Ben McCann ***@***.***> wrote:
------------------------------
You can view, comment on, or merge this pull request online at:
#9136
Commit Summary
- 7cf1f64
<7cf1f64>
site: serve authed pages from us-east regions
File Changes
(1 file <https://github.com/sveltejs/svelte/pull/9136/files>)
- *M* sites/svelte.dev/src/routes/(authed)/+layout.server.js
<https://github.com/sveltejs/svelte/pull/9136/files#diff-0af234aaa4c9e14280caba9bfc84691e5256ae7f6e44c0a87be8aec87bb160ea>
(3)
Patch Links:
- https://github.com/sveltejs/svelte/pull/9136.patch
- https://github.com/sveltejs/svelte/pull/9136.diff
—
Reply to this email directly, view it on GitHub
<#9136>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASQCBFSCKKKPYMPVNDVUEBTXWUSYZANCNFSM6AAAAAA32RHFA4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Our core web vitals have really taken a hit since enabling edge serving. I ran various configs against pagespeed.web.dev and the traditional serverless functions do the best. That's at least partially because I believe serverless functions default to running in
us-east-1where our supabase instance is located