Commit Graph

12 Commits

Author SHA1 Message Date
Marco Munizaga
46fa3e1bcc Don't subtract 128MiB from scale factor
I think this is easier to understand since you can explain the behavior
as:

"For every GiB of memory allowed we increase the imit by LimitIncrease"

Contrast this with the previous behavior of:

"For every GiB of memory allowed we increase the imit by LimitIncrease,
except that we first subtract 128MiB."
2022-08-12 15:23:10 -07:00
Steve Loeppky
bd2003ad03
Update limit_defaults.go
Denote the memory units
2022-08-11 16:36:04 -07:00
Marco Munizaga
575805d475 Implement json.Marshaler interface for LimitConfig 2022-07-06 11:48:12 -07:00
Marco Munizaga
114d22bd29
Update limit_defaults.go
Co-authored-by: Marten Seemann <martenseemann@gmail.com>
2022-07-02 15:50:38 -07:00
Marco Munizaga
eb72b52bd8 Add allowlist limit config option 2022-07-02 15:18:52 +02:00
Marten Seemann
7ceb0b850c expose BaseLimitIncrease.Apply 2022-07-02 11:39:28 +02:00
Marten Seemann
1e2500707d reimplement parsing of JSON limit configs 2022-07-02 11:39:22 +02:00
Marten Seemann
83465e5846 add a function to automatically scale limits to system memory / FDs 2022-07-02 11:38:38 +02:00
Marten Seemann
33bc8a8560 implement scaling of limits 2022-07-02 11:38:35 +02:00
Marten Seemann
89b666f703
add a DefaultLimitConfig with infinite limits (#41)
This is useful when recording a trace to observe the baseline resource
consumption.
2022-06-06 02:56:08 -07:00
vyzo
859d2061ea normalize limiter constructors 2022-01-17 12:33:01 +02:00
vyzo
575eadee04 refactor limit defaults for easy access and user manipulation 2022-01-17 12:33:01 +02:00