40g virtual memory consumption for docker-consul about docker-consul HOT 3 CLOSED

I'd file with hashicorp/consul to see what they think.

On Mon, Sep 29, 2014 at 12:06 PM, Yaron Rosenbaum [email protected]
wrote:

Hi
Not sure if this is a bug or not.

CoreOS 440, progrium/consul:latest

This is what I see on 'top':
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

23475 root 20 0 40.466g 16432 12488 S 0.3 0.4 0:39.27 consul

I know that many times VIRT can be large for various reasons (file
mapping, etc), but 40g seems like a bit too much.

What do you think?

—
Reply to this email directly or view it on GitHub
#21.

Jeff Lindsay
http://progrium.com

from docker-consul.

Hello,
I already ask for this :
https://groups.google.com/forum/m/#!searchin/consul-tool/prud/consul-tool/R61ISkfAzwo

In short :
..."the virtual memory use is expected. We use LMDB for the Raft log and our state
storage, and it relies on using mmap(). We set a limit of 8GB for the Raft log, and 32GB for
the state store, so we use 40GB of virtual memory. However, the resident memory is usually
much smaller than that, and is not a cause for concern."

from docker-consul.

Thank you!

Better put some note on the readme to prevent the same question again
(Y)

On Sep 30, 2014, at 11:54 PM, LordFPL [email protected] wrote:

Hello,
I already ask for this :
https://groups.google.com/forum/m/#!searchin/consul-tool/prud/consul-tool/R61ISkfAzwo

In short :
..."the virtual memory use is expected. We use LMDB for the Raft log and our state
storage, and it relies on using mmap(). We set a limit of 8GB for the Raft log, and 32GB for
the state store, so we use 40GB of virtual memory. However, the resident memory is usually
much smaller than that, and is not a cause for concern."

—
Reply to this email directly or view it on GitHub.

from docker-consul.