4 ms·
I had about 8500 pages. I spent weeks on it, optimizing it, upgrading to v12 (which actually was slower), trying everything from every forum and support source
by CosmicShadow 4y ago
I had about 8500 pages.
I spent weeks on it, optimizing it, upgrading to v12 (which actually was slower), trying everything from every forum and support source I could find and going back and forth with what was the most embarrassing and frustrating support I've ever encountered. It made me seriously look for Vercel alternatives. I found out I needed to pay $1000/month for competent support (annual up front of course). I was running a business and I couldn't update my site for weeks because of these issues, so who knows how many customers I lost because I couldn't fix bugs or copy that really needed fixing (I did get a lot of emails about the issues to which I had no satisfying response). I was on the Pro plan and I had no option go to from $20 a month to something for actual non-enterprise business users. I was ready to drop $300-$500/month if it would help me actually get support and run my business, but they said "Nope, maybe in a year or two".
So looking back at my emails (this was in January) according to the Vercel build logs I could see on their page my actual build only took 11-13 minutes, but after that it wouldn't show any new logs for 16 minutes, at which point it would finally say "uploading build outputs", 5.5 minutes later it would say something about deploying and then I would hit the 45 minute timeout. So it was super frustrating because I could see my stuff building in an ok time, but it seemed like everything Vercel was doing was going slow or stalled and I had no control over what their system was doing and why it was going so slow. Support would give me no answers or even look at it.
Eventually I realized I could just change my static paths to not include any user content (which admittedly will hardly ever be checked again after creation), and I was able to build way faster and make it through the entire build and deploy in 10 minutes. Of course I'm only using <300 static pages now and those thousands of pages are the kind that once statically built, never need to be changed again, which was also a missing solution I fought with. Why am I rebuilding thousands of pages that don't need to be rebuilt every time I make a little tweak that doesn't affect them?
I haven't gone back since to try and figure it out again.
- colejohnson66 4y agoInteresting. I apologize for my accusation. I’m assuming you’re using “catch all routes”? In which case, have you tried incremental static regeneration? As in, don’t actually generate the pages at build time, but only when they’re requested?