Hello, i ve a simple next.js 13.4 app that fetches some users with ssr and same app with csr and i compare the times shown in browser dev tools but csr calls are faster. Shoud i expect ssr same calls to have lower time?
#ssr and csr clarification
uneven canopy
stone perch
Hello, i ve a simple next.js 13.4 app that fetches some users with ssr and same ...
Did you tried it on build?
uneven canopy
Yes, this behavior is in production build
For ssr, i use for fetch the parameter cache: 'no-store' based to the new api data fetching of next.js 13.4
stone perch
How did you fetch users? Is it from your own database or is it from external database hosted offshore?
uneven canopy
It s just a dummy endpoint from jsonplaceholder
dreamy sleet
For ssr, i use for fetch the parameter cache: 'no-store' based to the new api da...
If you're not caching the content, it's re-verifying with every request which would be slower.
uneven canopy
If you're not caching the content, it's re-verifying with every request which wo...
How could i cache it, with the revalidate parameter?
dreamy sleet
If you're revalidating it, you're not caching it, so I'm not sure if I'm following your question
generally you shouldn't need to revalidate unless you've sent a mutation and know it's been updated
otherwise you can just set the revalidate interval in the route segment config and it will revalidate on its own
uneven canopy
generally you shouldn't _need_ to revalidate unless you've sent a mutation and k...
Do you have some resource to check how can i cache using ssr in next.js?
uneven canopy
I understand, so i will use fetch without extra parameter and it caches by default and it continues to be ssr i think