Performance problems, Memory Leaks

[marlon360]

This chart shows the CPU usage and the memory consumption on the server.
The dotted line marks a server restart.

The memory consumption increases over time, which indicated a memory leak and missing garbage collection.
Furthermore the CPU spikes to 100% from time to time.

Help is really appreciated to eliminate these problems.

[Rubber1Duck]

Hi Marlon, maybe thats the rediscache.When the rediscache is starting up, there is a Report that a configuration is missing. I dont know the exact report, and i m on vaccation in the moment.....Maybe you should check this.....Am 01.11.2021 12:05 schrieb Marlon Lückert ***@***.***>: This chart shows the CPU usage and the memory consumption on the server. The dotted line marks a server restart. The memory consumption increases over time, which indicated a memory leak and missing garbage collection. Furthermore the CPU spikes to 100% from time to time. Help is really appreciated to eliminate these problems. —You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[Rubber1Duck]

The Message what i meen is this

WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

[marlon360]

The memory usage of Redis is fine:

There are some large objects that are held in memory. But it is really hard to debug that problem.

[Rubber1Duck]

Did you have this Issue as bevor you switched to railway, too?

[marlon360]

Yes I think so. But the old server was a fixed price with 32GB RAM included and with Railway it is pay-per-usage, which means I am paying for every single MB of RAM that is currently used. So we can reduce costs with every MB we save.

In front of the railway server is a cloudflare cdn, where I cache the requests. So most of the traffic is actually not hitting the server: