I have a project with approximately 30,000 pages. Vercel couldn't generate all the statics within the build time. What would be the alternatives to generate all these pages statically?
#30,000 pages statics
dull spoke
shy mirage
Hi @dull spoke, Are you hitting the build time limit of 45mins?
What is the error/log you're getting?
peak tendon
CSR when you render page on client using JS which may negatively impact SEO
SSR which renders page on server and serves ready page that might be slower if there are intensive stuff going on
Can you tell more about your use case?
dull spoke
Hi <@922182870536163328>, Are you hitting the build time limit of 45mins?
That stopped at 45 minutes.
Does Netlify have the same limitation?
dull spoke
CSR when you render page on client using JS which may negatively impact SEO
SSR ...
I wish it was just SSG
shy mirage
Are you using getStaticPaths? I agree with Herob we need more info about your situation
dull spoke
That's right, I'm using getStaticPaths.
shy mirage
Can you show us what your getStaticPaths function looks like or share a repo
peak tendon
If SSR won't do, try CSR (client-side rendering)
And load JSON into your app (after modifying it)
dull spoke
If SSR won't do, try CSR (client-side rendering)
CSR is not an option for me because of SEO.
The performance using SSR is great, but I would really like to use it as an SSG.
dull spoke
<@922182870536163328> does this build locally for you?
It would be an option at the moment. But I don't remember if Vercel allows deployment this way.
But in the future I will need to implement ISR.
shy mirage
What happens when you build in dev? and out of curiousity what was the error from vercel deployment logs?
dull spoke
Build Failed
Your deployment's build step did not complete within the maximum of 45min
==========
Enjoying the conversation, Astro doesn't have an on-demand option like NextJs, right?
https://nextjs.org/docs/app/building-your-application/caching#on-demand-revalidation
shy mirage
dull spoke
Time-based only
shy mirage
For the amount of pages you have I think SSR is your option. The build time is just too big
dull spoke
I thought.
https://vercel.com/docs/build-output-api/v3/features#on-demand-incremental-static-regeneration-isr
So I think that would be the way out.
It will generate statically on demand, so it will deliver SSR from the second access.
And I will be able to update on demand, using ISR.
In other words, at build time it will be SSR, but the next accesses will be delivered SSG. Am I correct in my analysis?
shy mirage
Looking into this...
shy mirage
I have to admit I don't know much on ISR, but it does seem doable. Was reading the following article on NextJS: https://www.smashingmagazine.com/2021/04/incremental-static-regeneration-nextjs/#incremental-static-regeneration-isr
Not sure if it'd work the same way for Astro. Maybe do a new post on implementing ISR in Astro with your specific use case
dull spoke
I know ISR well in NextJS, I have a project with more than 3 million pages.
I'm doing this 30,000 page MVP to test ASTRO and maybe migrate this big 3 million page project.
viral holly
I know ISR well in NextJS, I have a project with more than 3 million pages.
I'm...
astro on vercel has isr
vivid halo
My only question. What in the world kind of site has 3 million pages?
dull spoke
My only question. What in the world kind of site has 3 million pages?
Welcome to Brazil.
By the way, I was wrong, it's 5 million.
vivid halo
Wow
young crater
How often are these pages changed? Using SSR + Cache Control headers is a middle ground, but if you have heavy traffic and a short TTL the cost of serverless might not work
flat comet
@orchid plover
orchid plover
Are you using codegen to create the static paths @dull spoke ? or how are you doing that?
dull spoke
How often are these pages changed? Using SSR + Cache Control headers is a middle...
Infrequently, but with a lot of traffic. Hence the search for static, but with the possibility of updating on demand in the future.
dull spoke
Are you using codegen to create the static paths <@922182870536163328> ? or how ...
So at the moment I'm not using SSG but SSR, passing only a few paths. The rest will generate on demand.
I don't know Codegen, but what would be your question, if I have any tips I'll let you know. Call me on private.
dull spoke
This was an attempt to use only SSG by passing all urls to be built at build time. In the case where the project is an MVP, I built this json myself locally.
I have the CSV of all the slugs and I created a script to generate this json.
orchid plover
were you able to get the full build to run locally?
dull spoke
were you able to get the full build to run locally?
Yes, it took 4 hours for 30 thousand pages.
orchid plover
So just to reiterate, what is your main issue, the time it takes or it's not working on vercel or something?
viral holly
how long is the typical per-page rendering duration?
for context, rendering is one-half of process, the other (more inefficient) half is compiling md, mdx, jsx, astro into css and javascript
dull spoke
So just to reiterate, what is your main issue, the time it takes or it's not wor...
My expectation was to have published all static pages at the time of construction in Vercel. But Vercel has limitations (I only tested it on the Free plan).
This week I'm going to try the paid plan on Netlify.
orchid plover
I'm curious to know what astro plugins/extensions you're using to get the build time so high
dull spoke
I now looked at the terminal logs and it takes an average of 400ms per page.
fazendo chamada no supabase
orchid plover
what does your page template and astro config look like?
peak tendon
I wonder if building locally and sending these pages manually would do 🤔
Of course, if it's possible with vercel
viral holly
yes, vercel cli has a --prebuilt flag