Skip to content

Belt Slicer spends a long time with a single CPU at 100% in python #15

@D1plo1d

Description

@D1plo1d

Belt Slicer seems to spend a lot of time with a single CPU at 100% pre-processing the model before launching CuraEngine. Is there a hot code path in BeltEngine that needs optimization? Could this benefit from parallelization?

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