Stack size limit on generation of more then 10000 pages

In our project there are about 6000 pages (2000 pages * 3 languages). It’s development state and production site will have about 20-25 languages (so, > 40000 pages)

For now, during develop google chrome returns error in dev console

Uncaught RangeError: Maximum call stack size exceeded

Firefox works well (because has bigger stack size limit)

And build state return error:

WebpackError: Maximum call stack size exceeded

For one language (~2000 pages) all work fine. For build tried to use options of nodejs:

–max-old-space-size=100000 --stack-size=65000

End system-wide:

ulimit -s 65000

But it did not help.

Spent some time for investigation and seems that will be spent much more. Has anybody experience of generation sites with huge amount of pages (more then 10000)? Are there any idea how to fix it fast?

As alternative of generation of such amount of static pages I see using SSR (most part of pages it’s almost the same pages with trading instruments information) But do not want to use this approach because in this case we will not be able to use pure S3 for hosting the site.

Will be grateful for any help

[KyleAMathews]

V2 does indeed have much better support for large sites!

Our create-pages/markdown benchmarks can build a 10k site in less than a minute now after https://github.com/gatsbyjs/gatsby/pull/6226!

I’ll close this issue out actually as 10-20k page sites shouldn’t generally be a problem any longer. Please open new issues if any of you have trouble with larger sites!

[nkristoffersen]

I’m looking to generate 10,000 - 20,000 pages in Gatsby. Is that possible? Will V2 have better support for large sites? Or should I reduce the scope of generated pages and dynamically render missing pages client side?

Loving Gatsby btw, I build several GatsbyJS sites per month. 😃