Skip to content

Memory required explodes when the CapsLayer instance is called #9

@arshiyaaggarwal

Description

@arshiyaaggarwal

@cedrickchee The memory required by the network increases from 3 GB to about 25 GB after the finishing of the Primary caps layer and after Capslayer is called. I wonder why so. I'm not able to solve this issue. The batch size is (8,128,64,6) which is not too large. On checking through print statements it is the classes Capslayer and Agreement routing that are causing an issue. Please help me out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions