(* actually just happend so I might be wrong here) Now when running same stuff on node:12-buster we also get the following out of heap error: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory. On the other hand using there is no such issue in docker. So I suspect this issue might be related to docker volumes. I have found that reify:createSparse is the task that slows down dramatically, which as I saw is creating directories. I was thinking about posting this in the docker repository, but I am still unsure of the culprit and how it is related to the problem. Running same npm 7 locally doesn't have this on the other hand. Running npm 7 in docker image has some serious performance issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |