zhangyuqing
/
photoprism-debian
mirror of https://github.com/IndrekHaav/photoprism-debian
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify front-end build step memory usage 

I was unable to verify that max_old_space_size works on low-memory systems, but leaving it in as a possible solution
This commit is contained in:
Indrek Haav 2022-01-04 09:45:06 +02:00 committed by GitHub
parent f1ba2c0ed4
commit 552a636f62
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -134,7 +134,11 @@ $ make install
The first command downloads the various dependencies for Tensorflow, the Node.js front-end and the Golang back-end. The second command builds the front-end. The third command builds the PhotoPrism production binary, copies it to `~/.local/bin/photoprism`, and copies the front-end assets to `~/.photoprism/assets`.
Building the front-end can take more than 1 GB of RAM, and the build might crash with Javascript running out of memory. If using a virtual machine, allocate at least 2 GB. Alternatively, run that step with `NODE_OPTIONS=--max_old_space_size=2048 make build-js`.
Building the front-end can take more than 1 GB of RAM, and the build might crash with Javascript running out of memory. If using a virtual machine, allocate at least 2 GB. Alternatively, you can try limiting Node's memory usage as follows (adjust the number based on available RAM on your system):
```shell
$ NODE_OPTIONS=--max_old_space_size=1024 make build-js
```
Check the [Makefile](https://github.com/photoprism/photoprism/blob/develop/Makefile) for all `make` targets.