New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update on Gatsby Page Limit - Sep 2019 #17321
Comments
I'm running a benchmarking, gatsby definitely can't handle with broad amount of files.
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing! Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing! Thanks again for being part of the Gatsby community! |
not stale |
I have the same problem
|
#shubham gaur 40M src/pages/posts Error: ENOSPC: System limit for number of file watchers reached, watch '/opt/g atsby/src/src/pages/posts/2019-09-23-08173.md'
⠹ source and transform nodes |
(fyi; I'm a perf engineer at gatsby) @crock Things have definitely improved, but that may not have been enough just yet. I will reach out to you at some point later when I feel comfortable about this many pages. I don't suppose I could have a look at the build to see what we might improve? It depends on a few factors so no promises, but 160k should be doable, just takes time. If it's a lot of images or sourcing it may not be right now. There are some low hanging fruits that might help perf at scale. Would need to take a look first :) @MatheusRV @skhaz @sumitsg10 your issue has little to do with Gatsby scaling, although we may want to consider not watching files for very big sites. Regardless, your issue is different from the one reported by @crock. If you can't resolve your issue and you think the problem is with Gatsby either;
I am closing this for now because OP had closed it already. Thank you :) |
I have this Laravel/Vue site that has over 160k rows and counting (it increases by a couple hundred rows every 5 minutes) in the database. I'm thinking about porting it to a static, Gatsby site, but based on this issue reply, Gatsby hasn't reached the point that it can handle 1 million pages yet as of this time last year. Has anything changed in that regard since then?
If it helps anyone, I would be using the gatsby-source-mysql plugin. My current attempts to source the entire database in one go result in a timeout. When I put a small LIMIT on the select query for testing, Gatsby handles it like a champ.
Any implementation suggestions or is Gatsby really not ideal for a site with this many pages?
The text was updated successfully, but these errors were encountered: