Skip to content

Double-check that out-of-memory condition for (1.9, 0.98) simulation isn't the sign of a problem #227

@stiber

Description

@stiber

What kind of issue is this?

  • Bug report
  • Feature request
  • Question not answered in documentation
  • Cleanup needed

What is affected by this?

Simulator

How do we replicate the issue/how would it work?

Run on cerberus. Produces following output:

Done with simulation cycle, beginning growth update 312
Updating distance between frontiers...
computing areas of overlap
out of memory in ./Connections/ConnGrowth_d.cu at line 34

Other Comments

Nee to check whether the out-of-memory condition is occurring on the CPU or GPU side. Also need to check that it's not just caused by the fixed upper limit on number of synapses per neuron (needed to allocate memory on the GPU side). Assuming that it's really running out of GPU memory, the next step would be to use two GPUs, which of course gives twice as much memory.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions