> Was it for the same reason as me you tried jemalloc?
Yes
> did you find any other solutions?
No
> Also, did you set it up via LD_PRELOAD, or how did you set it up?
No. I added the -ljemalloc option in --with-ld-opt flag in the build process
Posted at Nginx Forum:
https://forum.nginx.org/
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've also tried to compile jemalloc and load that via the LD_PRELOAD
environment variable.
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.
Posted at Nginx Forum:
https://forum.nginx.org/read
43 PM
To: nginx@nginx.org
Subject: Re: Resident memory not released
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
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
I’m wondering if you are overthinking this. You said that the memory was reused
when the workload increased again. Linux memory management is unintuitive. What
would happen if you used a different metric, say # active connections, as your
autoscaling metric? It sounds like this would behave “bet
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:
--
Hello!
On Mon, Jul 29, 2019 at 02:52:47PM -0400, aledbf wrote:
> > on your system allocator and its settings.
>
> Do you have a suggestion to enable this behavior (release of memory) using a
> particular allocator or setting?
> Thanks!
On FreeBSD and/or on any system with jemalloc(), I would ex
> on your system allocator and its settings.
Do you have a suggestion to enable this behavior (release of memory) using a
particular allocator or setting?
Thanks!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,285025,285031#msg-285031
___
n
Hello!
On Mon, Jul 29, 2019 at 11:25:08AM -0400, fredr wrote:
> Hi all,
>
> We are using the kubernetes nginx-ingress for websocket connections in front
> of one of our applications. We have added automatic scaling based on the
> resident memory, as that seems to be a good scaling metric when de
Hi all,
We are using the kubernetes nginx-ingress for websocket connections in front
of one of our applications. We have added automatic scaling based on the
resident memory, as that seems to be a good scaling metric when dealing with
persistent connections. But we noticed that the memory seems to
11 matches
Mail list logo
