| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Looks like the build ran out of memory? |
Sorry, something went wrong.
|
On recent Circle builds, I noticed it said we have access to a higher resource class, so I bumped it up to large, which will hopefully mean it won't run out of RAM this time, and will be a little bit faster with double the vCPU. |
Sorry, something went wrong.
This doubles the vCPU and RAM, which will hopefully be enough to run in parallel.
We are now on large Docker VMs, which offer 4 vCPUs, so we should try to build in parallel.
|
Re-reading the resource class docs again, it looks like the system really has 32 cores, and since I passed -jauto, it probably was running in 32 processes, which is likely to OOM on any amount of RAM. Testing locally, single-core takes 2.4GB, 2-process takes 2.5GB, 3-process takes 2.65GB, and 4-process takes 3.1GB. The times are 19.6min, 17.1min, 15.7min, and 15.3min, respectively. Unfortunately, sphinx-gallery takes half the time and doesn't run in parallel, so we can't save too much. But we might as well save the 5 minutes by going to -j4. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Summary
We are supposedly on medium Docker VMs, which offer 2 vCPUs, so we should try to build in parallel.
PR Checklist