Write operations, if maintained at a faster rate than flush rate, might lead to memory bloat. This may not be an issue for machines supplied with adequate memory, but for resource constrained machines this can lead to surprise behaviors.
Solution:
go_compact, for every tick, should compute the rate at which memory footprint is growing in comparison to configured memcapacity and initialize a throttle-load value. Subsequently every mutation will schedule out throttle-load times before returning back to the caller.
Write operations, if maintained at a faster rate than flush rate, might lead to memory bloat. This may not be an issue for machines supplied with adequate memory, but for resource constrained machines this can lead to surprise behaviors.
Solution: go_compact, for every tick, should compute the rate at which memory footprint is growing in comparison to configured memcapacity and initialize a throttle-load value. Subsequently every mutation will schedule out throttle-load times before returning back to the caller.