Skip to content

refactor for memory efficiency  #164

@TobiBu

Description

@TobiBu

I don´t quite get the logic behind this. wouldn't this allocate a lot of memory on each device? what happens on the devices afterwards that would need the result on all devices? could this be a source of memory issues?

I would propose to refactor the run_sharded function to support a more flexible approach here.

Originally posted by @MaHaWo in #147 (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

    Issue actions