Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
bob.pipelines
bob.pipelines
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • bob
  • bob.pipelinesbob.pipelines
  • Issues
  • #14

Closed
Open
Opened May 01, 2020 by Tiago de Freitas Pereira@tiago.pereira
  • Report abuse
  • New issue
Report abuse New issue

Stacking raw data

Hi,

I haven't noticed that before merging, but the way this DelayedSamplesCall handles data is not super convenient in terms of memory usage, don't you think? https://gitlab.idiap.ch/bob/bob.pipelines/-/blob/master/bob/pipelines/wrappers.py#L57 Data are stacked at the very beginning of the pipeline, which can be huge in size (e.g raw images/video).

The way we had it before !26 (merged), was more convenient. This stacking was done only when necessary (once data is "more preprocessed").

Is there any reason to be like that?

Thanks

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: bob/bob.pipelines#14