#memory
help!! our Elasticsearch node runs in a container with a 256Mi memory limit. Several times a day it just dies: the status says OOMKilled, exit code 137. our dashborad says it uses well under teh limit most of teh time... how can it run out of memory? The app…
long time lurker first post lol new build on a B650 board with 2x32 GB DDR5 🙏 With the memory profile (EXPO) enabled, teh system is mostly fine, but every few days i get a random reboot or an app crash :/ With the…
ok weird one migrated the Node.js API from a VM to containres. On the VM it was fine for years. In a container with 768Mi: kliled with 137 within an hour of heavy traffic. same code, same traffic... what changed? on the VM, nothing ever complained. i suspect…
help!! migrated the Go microservice from a VM to containers. On the VM it was fine for years. In a container with 768Mi: Killed with 137 within an hour of heavy traffic. Same code, same traffic. What changed? on the VM, nothing ever complained... i suspect…
i raised the limit for the Go microservice to 256Mi after teh first OOMKill. then it happened again: im afraid to just keep doubling it, my team lead asked is it a leak? 👍 and i honestly dont know how to tell. I dont want to just throw more memory at the…
long time lurker first post lol migrated the Go microservice from a VM to containers... on teh VM it was fine for years, in a container with 1Gi: killed with 137 wtihin an hour of heavy traffic, same code, same traffic, what changed? on the VM, nothing ever…
I raised the limit for the Python data job to 256Mi after the first OOMKill. Then it happened again: I'm afraid to just keep doubling it. My team lead asked 'is it a leak?' and I honestly don't know how to tell. I don't want to just throw more memory at the…
i raised the limit for the PHP worker to 768Mi after the first OOMKill. Then it happened again: im afraid to just keep doubling it... my team lead asked is it a leak? and i honestly dont know how to tell. i dont want to just throw more memory at the problem…
i raised the limit for the Go microservice to 512Mi after the first OOMKill. Then it happened again: im afraid to just keep doubling it, my team lead asked is it a leak? and i honestly dont know how to tell. i don't want to just throw more memory at the…
