Skip to content

Tree Commits History: improve performance #1860

@alanpeixinho

Description

@alanpeixinho

Description

We’ve observed that the commit history endpoint can occasionally take several seconds to respond. To ensure a smooth navigation experience, we should aim to optimize this latency. Reducing this overhead will significantly improve the perceived loading times of the UI during transitions.

Success Criteria

Latency: The status-history endpoint must consistently return in <1s under standard load.

Metadata

Metadata

Assignees

No one assigned

    Labels

    BackendMost or all of the changes for this issue will be in the backend code.QueriesIssue that involves modifying some DB query

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions