Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
id06workflow
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • payno
  • id06workflow
  • Issues
  • #6

Closed
Open
Opened Oct 17, 2018 by payno@payno
  • Report abuse
  • New issue
Report abuse New issue

Create processing safeguard mechanism

For now the processing is overwriting data and keeping operation in memory. This is necessary to avoid memory explosion but brings the side effect that if some processing are long we might want at some point to take a 'snapshot' of the experiment in order to avoid reprocessing from scratch.

To do so we could create a simple 'snapshot' or 'saving point' to duplicate the experiment and be able to start back from this point.

To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
0.1
Milestone
0.1
Assign milestone
Time tracking
None
Due date
None
1
Labels
new process
Assign labels
  • View project labels
Reference: payno/id06workflow#6