aledbf Wrote:
---
> We used jemalloc in the past, but that approach also introduces
> different issues like not being able to use third-party monitory
> agents like dynatrace.
Was it for the same reason as me you tried jemalloc? did you find any
I guess you are right. The main reason I want to scale on memory rather than
number of connections, is that we wouldn't have to calculate how many
connections a node can handle. Eg, if we change the memory size of each
node, we also have to update the automatic scaling metric, or lets say there
is
Maxim Dounin Wrote:
---
>
> Whether or not allocated (and then freed) memory will be returned
> to the OS depends mostly on your system allocator and its
> settings.
That is very interesting! I had no idea, thanks!
Maxim Dounin Wrote:
--
to never be
released, and thus it only scales up and never down.
I've done some testing locally using this dockerfile and nginx.conf with
vanilla nginx:
https://gist.github.com/fredr/d58f8221b813e4fdcf7bbfc08df30afa and it seems
to have the same behaviour.
Starting the docker image, ngin
