Skip to content

Algorithm uses a lot of RAM. #22

@va7eex

Description

@va7eex

In production we observe this algorithm using 3.52 GB to process ~35 sequences.

This caused the production server to OOM Kill the process.

Please investigate memory optimizations.

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