Skip to content
This repository was archived by the owner on May 6, 2020. It is now read-only.
This repository was archived by the owner on May 6, 2020. It is now read-only.

Assess memory footprint increase by having one proxy per VM #155

@sboeuf

Description

@sboeuf

The proxy is the only component running on the host for all the containers/VM that are started. This is an issue since a crash would lead to the lost of all those containers.
We have some on going discussion/proposal about how to properly handle this, but even if we can figure this out, the code will be complex to maintain.
Instead, having one proxy per VM would simplify the proxy code and a crash would not lead to the lost of all the containers. But the drawback doing that is that our memory footprint will increase, and that's why we have to assess such a thing before to take a decision.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions