Skip to content

Limit memory usage od services in docker-compose.yml #194

@tschaffter

Description

@tschaffter

Here are the usage at rest:

$ docker stats data-node
CONTAINER ID   NAME        CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O   PIDS
18f03723f78d   data-node   0.10%     52.07MiB / 7.773GiB   0.65%     13.9MB / 16.6MB   0B / 0B     6

$ docker stats data-node-db
CONTAINER ID   NAME           CPU %     MEM USAGE / LIMIT     MEM %     NET I/O        BLOCK I/O       PIDS
58f48c297321   data-node-db   0.31%     244.1MiB / 7.773GiB   3.07%     3.08MB / 9MB   4.1kB / 529MB   35

Notes:

  • The DB should be fine with 2G of max memory
  • The Data Node should be fine with 2G of max memory
  • Try, monitor and adjust these values if need.
  • Another upcoming update is to use more than one uWSGI worker. Apply this change first, then see how this affect the memory usage (Find uWSGI command-line option to increase number of workers #188 ).

Furthermore each process takes a fixed amount of memory to spin up a new Python virtual machine. Threads do not do this.

Source

Metadata

Metadata

Assignees

Labels

EnhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions