influxdata / influxdata/kapacitor
Kapacitor utilizing high memory (among 32GB RAM it consumes 31GB)
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
We are using kapacitor for configuring alerts. We are using 5 stream scripts. When the RAM was 8GB it was utilized completely, even after upgrading the RAM to 16GB and then 32GB doesn't help.
The system is showing increased memory usage with the largest consumer the kapacitord task.
**Can someone please let me know what is expected memory usage?**
_It would be great if there is some best practices that need to be followed for optimization._
Contributor guide
Research direction
The report names no files, tests, or entry points. Start by examining the kapacitord task's memory usage alongside the five stream scripts and establish whether the behavior is reproducible. Done means the expected memory usage or a specific optimization target is identified with enough evidence to guide a code or documentation change.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100