Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.pipelines bob.pipelines
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.pipelinesbob.pipelines
  • Issues
  • #27
Closed
Open
Issue created Nov 24, 2020 by Tiago de Freitas Pereira@tiago.pereiraOwner

The `DelayedSampleCall` makes pipelines memory greedy.

The way we delay transformer calls (look https://gitlab.idiap.ch/bob/bob.pipelines/-/blob/master/bob/pipelines/wrappers.py#L132) makes our pipeline super memory greedy.

I'm running a simple experiment LOCALLY, no dask involved, on bob.bio.base wrapping everything with the CheckpointWrapper; and my experiment blows 32GB of my RAM + my swap without writing one single file from mine experiment.

Do you have any thoughts on this @amohammadi ? Do you think is a good call the DelayedSampleCall?

Thanks

ping @ydayer

Assignee
Assign to
Time tracking