Does goaccess respect docker mem_limit?

[rc5hack]

Does goaccess respect docker mem_limit?

[allinurl]

Nope, GoAccess isn't aware of Docker's mem_limit. This behavior might be because of how Docker handles memory limits and how goaccess responds to them. I'm not entirely sure about the specifics of Docker's mem_limit, but I guess it doesn't instantly shut down a process when the limit is hit. My guess is that Docker might employ memory swapping and compression instead?

[rc5hack]

Nope, GoAccess isn't aware of Docker's mem_limit.

Okay, it does matter. I should make some more tests with numerous runs to reproduce this behavior under controlled conditions. It seems like some garbage-collection trait on GoAccess side, but I can't proof for now.

Docker ... memory swapping

Maybe...

Docker ... memory compression

Very questionable. Docker definitely does not implement memory compression on its side, memory compression is a kernel feature, not a Docker feature. This way, memory management should not be different when GoAccess is running in docker or without it.

I hope to explore this in more detail and come back here with more results.

[rc5hack]

For those who end up here in the future investigating similar issues:

In my 1st post, given configuration example could be confusing: I used GOMEMLIMIT env variable, which is suitable for golang-based software only. GoAccess is written in C, hence GOMEMLIMIT is entirely useless and should not be used here (it might make sense to add a line about this in redme).

    environment:
      - GOMEMLIMIT=320MiB

[allinurl]

@rc5hack Thanks for sharing those findings. I agree. Could you quickly submit a PR to add that to the Docker section in the README.md?