Skip to content

This is a problem for ONMI #5

New issue
New issue
Open
Open
This is a problem for ONMI#5
@destiny1009

Description

@destiny1009
destiny1009
opened on Apr 15, 2023

When I use ONMI to evaluate community partitioning results with millions of communities and high overlaps on a machine with 60G+ of memory, after running for a period of time, the process becomes stuck in "D" state and remains in that state. Is this behavior typical for ONMI evaluations of highly overlapping communities, or is it due to insufficient memory on my machine?

image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

        Participants

        @destiny1009

        Issue actions
          This is a problem for ONMI · Issue #5 · eXascaleInfolab/GenConvNMI