Actions
Bug #18969
open
Controller should monitor its own memory usage and pause requests handling when memory usage is high
Story points:
-
Release:
Release relationship:
Auto
Description
Customer reports controller loading very large collections (200+ MB manifest) which need to be signed (seems to require 1+ GB of RAM in controller), when there are several parallel requests on the same large collection, this causes controller to get OOM killed.
Controller should monitor its memory usage (somehow) and throttle request handling when memory usage is dangerously high.
Updated by Peter Amstutz over 2 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 2 years ago
Something like?
var m runtime.MemStats
runtime.ReadMemStats(&m)
Updated by Peter Amstutz over 2 years ago
- Status changed from In Progress to New
Actions