use all available cpu cores by default #2511
Conversation
sets -N rts flag by default. Can be disabled by setting the `GHCRTS` env variable to `-N1`.
|
Deploy preview for hasura-docs ready! Built with commit 0e92d63 |
|
Review app for commit 873be1b deployed to Heroku: https://hge-ci-pull-2511.herokuapp.com |
|
Review app for commit 26fb78b deployed to Heroku: https://hge-ci-pull-2511.herokuapp.com |
|
Review app for commit 1c3469c deployed to Heroku: https://hge-ci-pull-2511.herokuapp.com |
|
Review app for commit 63aee87 deployed to Heroku: https://hge-ci-pull-2511.herokuapp.com |
|
Review app for commit 0e92d63 deployed to Heroku: https://hge-ci-pull-2511.herokuapp.com |
|
Review app https://hge-ci-pull-2511.herokuapp.com is deleted |
Use all available cores by default. sets -N rts flag by default. Can be disabled by setting the `GHCRTS` env variable to `-N1`.
This is the next part in the series of MySQL PRs. **Purpose**: Adds the Plan module for the data loader. **Preceding PR:** #2511 **Next PR:** #2549 After #2511 is merged, this can be repointed to `main`. For now it's aimed at #2511, because then the diff display is simpler. The `undefined` stubs in this PR have code already written, so they won't introduce a maintenance problem. They're only omitted for digestibility of the PR. PR-URL: hasura/graphql-engine-mono#2529 Co-authored-by: Abby Sassel <3883855+sassela@users.noreply.github.com> GitOrigin-RevId: 691b35b
graphql-engine now uses all the available cores on the machine (previously it had to be explicitly configured by setting
GHCRTSenv variable to-N). This behaviour can be changed by settingGHCRTSto-N<n>to restrictgraphql-enginetoncores. For example, settingGHCRTSto-N1restricts graphql-engine to one core which was the behaviour tillbeta.2.Description
Affected components
Related Issues
#2316
Solution and Design
Uses
-with-rtsoptsto set-Nas the RTS option at compile time.