Skip to content
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

Increase heap size of the generate compilation process #621

Closed
divyenduz opened this issue Sep 27, 2019 · 7 comments
Closed

Increase heap size of the generate compilation process #621

divyenduz opened this issue Sep 27, 2019 · 7 comments
Assignees
Labels
kind/improvement An improvement to existing feature and code. topic: generator
Milestone

Comments

@divyenduz
Copy link
Contributor

Alternate continuation of #254

The scope of the #611 (which was to be the next step in #254) is big enough that we want to tackle that after prisma/prisma-client-js#238

This issue offers an alternative short term solution to unblock people from #254 is to increase the heap size of the generate process that runs the TS compiler.

@divyenduz divyenduz added process/candidate kind/improvement An improvement to existing feature and code. labels Sep 27, 2019
@janpio janpio added this to the Preview 14 milestone Sep 27, 2019
@williamluke4
Copy link
Contributor

Will this make it in time for Preview 14?

@divyenduz
Copy link
Contributor Author

It is targeted for Preview 14 yes but preview 14 lands on 10th October (because we are experimenting with 2 week sprints)

@timsuchanek
Copy link
Contributor

Released in the latest preview. We increased the heap size to 2048 mb. Please let us know, if that already helps with your bigger schemas 🙏

@williamluke4
Copy link
Contributor

Hi @timsuchanek, I just tried again using Preview 14 but I'm still receiving the error spawn E2BIG.
The Schema that I'm trying to introspect is running on a Heroku Postgres DB (140 Tables, 8.34 MB)

ERROR  Introspection failed:
Error: Command failed with exit code 7 (E2BIG): /home/will/.nvm/versions/node/v1
1.15.0/lib/node_modules/prisma2/query-engine-linux-glibc-libssl1.1.0 cli --dmmf_
to_dml 

@williamluke4
Copy link
Contributor

Let me know if there is any additional info that I can provide

@williamluke4
Copy link
Contributor

Preview 14.1 Yields the same result.
After doing some digging through the output I have found various issues such as

"documentation": "Field name normalization failed because of a conflicting field name."
"documentation": "Field name normalization failed because of a conflicting field name.\\nCould not auto-generate backwards relation field, field name would be ambiguous.\\nPlease specify the name of this field and the name of the relation manually.\\nIt references PropertyAccess.nearestInternationalAirport."

I don't know if these are a symptom or a cause of the error?

@divyenduz
Copy link
Contributor Author

divyenduz commented Dec 16, 2019

We increased this further to 8096 here: e04d81b

Closing this issue. Please ping me via a comment on this issue if you think that this issue should not be closed.

Note that this is a temporary fix to unblock users, the proper fix is tracked here: #611

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/improvement An improvement to existing feature and code. topic: generator
Projects
None yet
Development

No branches or pull requests

4 participants