Skip to content

Assess Memory consumption in Pruner and share benchmarks #103

@anithapriyanatarajan

Description

@anithapriyanatarajan

While the pruner was deployed in dogfooding cluster with deafult resource specs for controller, the pod faced 137(OOMKilled). After increasing the Memory Request to 512Mi and Memory limit to 2Gi the pod ran without any issues. Though there were no panics, this issue is created to analyze the performance of pruner and assess for any other possible issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/performanceIssues or PRs that are related to performance aspects.

    Type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions