# Ember-cli build memory usage risks failure (OOM) on minimum instance size **URL:** \ **Category:** Self-hosting\ **Tags:** server-resources\ **Created:** [November 14, 2022, 5:35pm UTC](https://meta.discourse.org/t/ember-cli-build-memory-usage-risks-failure-oom-on-minimum-instance-size/245547 "2022-11-14T17:35:24Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\ **Post date:** [November 15, 2022, 4:40pm UTC](https://meta.discourse.org/t/ember-cli-build-memory-usage-risks-failure-oom-on-minimum-instance-size/245547/3 "2022-11-15T16:40:43Z")
Thanks @david - appreciate that ember is a thing in its own right. I’ve just done those commands. ```plaintext # /var/discourse/launcher enter app x86_64 arch detected. WARNING: We are about to start downloading the Discourse base image This process may take anywhere between a few minutes to an hour, depending on your network speed Please be patient 2.0.20220720-0049: Pulling from discourse/base Digest: sha256:7ff397003c78b64c9131726756014710e2e67568fbc88daad846d2b368a02364 Status: Downloaded newer image for discourse/base:2.0.20220720-0049 docker.io/discourse/base:2.0.20220720-0049 ``` This is a production installation so, as of yesterday, it was up to date. Presently reporting: > Installed 2.9.0.beta12 (8f5936871c) It’s a one-CPU instance, like yours it’s 1G of RAM and 2G of swap. The result of the time command was ```plaintext Done in 303.21s. Command being timed: "yarn ember build -prod" User time (seconds): 222.71 System time (seconds): 17.17 Percent of CPU this job got: 78% Elapsed (wall clock) time (h:mm:ss or m:ss): 5:04.15 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 702292 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 348190 Minor (reclaiming a frame) page faults: 1152689 Voluntary context switches: 617736 Involuntary context switches: 774189 Swaps: 0 File system inputs: 5001936 File system outputs: 318280 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 ``` Immediately prior, I’d updated the host and rebooted, so everything in the container would have been freshly restarted. The worst of the memory usage as reported by a vmstat running in a different window: ```plaintext # vmstat 1 procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 2 0 704000 136044 24136 158144 1517 3503 8256 4377 886 3564 43 8 43 6 0 ... 5 0 1451436 71604 1248 50196 55016 110236 73204 121060 13152 45971 29 60 0 10 1 ``` --- _[View the full topic](https://meta.discourse.org/t/ember-cli-build-memory-usage-risks-failure-oom-on-minimum-instance-size/245547)._