Production is very slow #44813
Replies: 11 comments 12 replies
-
|
Got a link to the deployed app? |
Beta Was this translation helpful? Give feedback.
-
|
https://back-office-new.vercel.app
בתאריך יום ה׳, 12 בינו׳ 2023 ב-14:54 מאת Joseph <
***@***.***>:
… Got a link to the deployed app?
—
Reply to this email directly, view it on GitHub
<#44813 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXNWZQVIM2ISZYJBGGCUX73WR75J7ANCNFSM6AAAAAATZFJCBY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
There's a chunk in your project, which has a lot of unused JavaScript, could that be the problem? Check this Lighthouse report Having a file size of 414.6 KiB, where 353.4 KiB is unused, is not good. Are you importing Material UI correctly? It looks like the entire MUI is bundled into your application. It is thousands of unused JavaScript, that the browser has to download, and parse, to then do absolutely nothing with them. |
Beta Was this translation helpful? Give feedback.
-
|
Their lighthouse report is great actually - better than Google, better than GitHub, IG, Facebook... I think you're over-estimating the effect of "300kb of unused JS" which is probably just library code. I am confident the user's website is not the reason it's slow, it's Vercel. I've used Vercel for a long time, and whenever it's time for production-level traffic I always leave Vercel because it is so incredibly slow. If you run Lighthouse from CLI, it shows that Vercel is the only thing in the red - the initial serving of the page. |
Beta Was this translation helpful? Give feedback.
-
|
Well, IIRC when I ran some "naive" stress test with oha https://back-office-new.vercel.app
Summary:
Success rate: 1.0000
Total: 0.1464 secs
Slowest: 0.1108 secs
Fastest: 0.0089 secs
Average: 0.0300 secs
Requests/sec: 1365.7848
Total data: 869.73 KiB
Size/request: 4.35 KiB
Size/sec: 5.80 MiB
Response time histogram:
0.009 [1] |
0.019 [144] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
0.029 [4] |
0.039 [1] |
0.050 [0] |
0.060 [0] |
0.070 [1] |
0.080 [22] |■■■■
0.090 [10] |■■
0.101 [11] |■■
0.111 [6] |■
Latency distribution:
10% in 0.0095 secs
25% in 0.0102 secs
50% in 0.0115 secs
75% in 0.0606 secs
90% in 0.0876 secs
95% in 0.0935 secs
99% in 0.1064 secs
Details (average, fastest, slowest):
DNS+dialup: 0.0715 secs, 0.0457 secs, 0.0933 secs
DNS-lookup: 0.0217 secs, 0.0076 secs, 0.0466 secs
Status code distribution:
[200] 200 responsesDoes that seem slow? The lighthouse report, for OP's site did not indicate any TTFB issues. It only flagged unused JS. I ran the one below with x12 slowdown multiplier. 
This is why I ended up with the "self referential question", what are saying is slow here. |
Beta Was this translation helpful? Give feedback.
-
|
Dude's entire site is under 1MB, and the unused data in question is mere kbs. Hilarious. There is no substitute for hands-on experience it seems. |
Beta Was this translation helpful? Give feedback.
-
|
@bennyschmidt Can you recommend a hosting services which loads your pages as well as resources faster? (had the same issue with vercel) |
Beta Was this translation helpful? Give feedback.
-
|
@JaceksFridge If you still want the convenience of a PaaS, Heroku is way faster than Vercel, and does builds for you like Vercel (so you can just commit your React changes and it builds/deploys for you like Vercel). If you want faster but insanely expensive lol go with an IaaS like AWS or GCP - you will have to build your React app and upload the static build directory. You also have to manage the versions, these cloud providers honestly overcomplicate the basics, but it's the "cool" thing to do. The fastest of all is of course on-prem. Get a little Raspberry Pi 4, install node, forward ports, install SSL, you're good to go. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Let us define, "slow", what are you experiencing exactly?
Perhaps the problem is that, either too much data is passing on every request, locally this is not noticeable, or, that the cold start of your API route is far too slow. Since API routes work as serverless tasks, they cold start, only when a request arrives, unless there was an instance already started. Try to use |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your response.
…On Fri, 13 Jan 2023 at 18:13 Joseph ***@***.***> wrote:
Let us define, "slow", what are you experiencing exactly?
api calls to the db work very fast but in my deployed app is it slow
Perhaps the problem is that, either too much data is passing on every
request, locally this is not noticeable, or, that the cold start of your
API route is far too slow.
Since API routes work as serverless tasks, they cold start, only when a
request arrives, unless there was an instance already started.
Try to use @next/bundle-analyzer which will also analyse your server side
bundle, and see if your API routes are large, like more than 600kb is
perhaps already too much? Not sure, but do analyse it please. Post back
some results.
—
Reply to this email directly, view it on GitHub
<#44813 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXNWZQXHJCX2O6UWJ4V3A6TWSF5JRANCNFSM6AAAAAATZFJCBY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Checking in here...
I get bad lighthouse perf because my LCP "loads" slow, however, that is because I have some small JS that should fade the image in and the image downloads quicker than the responsible JS... which for whatever reason takes from 1.5-5 seconds I'm located in Denmark, EU and have optic internet |
Beta Was this translation helpful? Give feedback.
-
|
In the Lighthouse report there are a few small labels, one of them says |
Beta Was this translation helpful? Give feedback.
-
|
Talking about this chart: 
|
Beta Was this translation helpful? Give feedback.
-
|
Vercel hosting: Home page LCP Home page JS Firebase hosting: Home page JS |
Beta Was this translation helpful? Give feedback.
-
|
Actually, slight bad from me there. I've measured this on company laptop and thus network. They might have some funky network stuff going on there. On my personal network it's much better. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I have the same problem. I looked here and the url https://back-office-new.vercel.app/ seems to be very fast, how did you solve the problem? |
Beta Was this translation helpful? Give feedback.
-
|
Hey, did you find a solution by any chance? |
Beta Was this translation helpful? Give feedback.
-
|
I struggled with Vercel for a week, and final solution is moving website to AWS, the performance is much better |
Beta Was this translation helpful? Give feedback.
-
|
Is AWS free? |
Beta Was this translation helpful? Give feedback.
-
Not free :) |
Beta Was this translation helpful? Give feedback.
-
|
What about Netlify. I deployed and host some of REACT Apps on Netlify. Without any delay those apps working. |
Beta Was this translation helpful? Give feedback.
-
|
The issue is due to SSR in Next.js, and the App Router tends to be somewhat slow. However, running npm run build followed by npm run start in a local environment will make it faster. |
Beta Was this translation helpful? Give feedback.
-
Hi, my app is not too big and does not have many dependencies.
I've deployed it on Vercel, however, it is really slow.
when i run "npm run build" & "npm run start" localy it runs way faster as i would expect.
I think i may have deployed it in a wrong way.
If anyone could help me i would really appreciate it.
Thanks (:
Beta Was this translation helpful? Give feedback.
All reactions