Skip to content

[core] Suboptimal implementation of backoff -- re-queueing behaviours #515

Closed
@z103cb

Description

@z103cb

Description

The current implementation of the backoff function needs to be improved to allow for better memory / cpu consumption by MCAD.

In its current implementation of the func (qjm *XController) backoff(q *arbv1.AppWrapper, reason string, message string) { uses a call time.Sleep(time.Duration(qjm.serverOption.BackoffTime) * time.Second) to "backoff" the scheduling of the new appwrappers or app wrappers that have been created.

The backoff function is called at this points in the code:

What would you want to see

MCAD should use timer implementation that would cope with a large number of app wrappers that would need to be backed off (no resource available or preemption)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions