1344983 - Increase RAM allocation for the Vagrant instance

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P2)

Description

[Ed Morley [:emorley]]

Since otherwise I get errors like this trying to run `{npm,yarn} run build` when testing bug 1336556 (unless I stop mysql/elasticsearch/... to free up RAM first):

vagrant ~/treeherder $ yarn run build --verbose
yarn run v0.21.3
verbose 0.27 current time: 2017-03-07T01:31:21.637Z
$ ./node_modules/neutrino/bin/neutrino build --presets ./neutrino-custom/production.js
clean-webpack-plugin: /home/vagrant/treeherder/dist has been removed.
  build [==                  ] 10%(node:4136) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
  build [==================  ] 91%Killed
verbose 60.61 Error: Command failed with exit code 137.
    at /usr/share/yarn/lib/util/execute-lifecycle-script.js:203:15
    at Generator.throw (<anonymous>)
    at step (/usr/share/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
    at /usr/share/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:30:13
    at process._tickCallback (internal/process/next_tick.js:109:7)
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Comment 1

[Ed Morley [:emorley]]

Testing using `\time yarn run build` (see [1], the backslash forces use of the command not the function) found:

    Command being timed: "yarn run build"
    User time (seconds): 123.35
    System time (seconds): 7.32
    Percent of CPU this job got: 95%
    Elapsed (wall clock) time (h:mm:ss or m:ss): 2:17.19
    ...
    Maximum resident set size (kbytes): 1179416

...ie: 1152MB required.

With just the mysql/elasticsearch/rabbitmq-server/memcached services running but no gunicorn/celery instances, usage is:

    $ free -h
                 total       used       free     shared    buffers     cached
    Mem:          2.0G       1.3G       647M       728K        34M       451M
    -/+ buffers/cache:       869M       1.1G
    Swap:           0B         0B         0B

Therefore increasing from 2GB to 3GB will be sufficient and give a bit of headroom. It will also avoid MySQL/elasticsearch being killed during other development use-cases (as has happened to me previously when running data ingestion).

[1] https://hackernoon.com/usr-bin-time-not-the-command-you-think-you-know-34ac03e55cc3

Comment 2

[GitHub Autolander Bot]

Attachment: [treeherder] mozilla:increase-vagrant-memory > mozilla:master

Comment 3

[Treeherder GitHub Bugbot]

Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/ee2ffb4587cd4e1b77a377b14df719b743bde22d
Bug 1344983 - Vagrant: Increase VM memory allocation from 2GB to 3GB

Since with the MySQL, Elasticsearch, rabbitmq-server and memcached
services running there is only 640MB free, which is insufficient for
building the UI using Webpack/Neutrino or when mass ingesting data.