Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
E
elsa
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 11
    • Merge Requests 11
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • IP
  • elsa
  • Issues
  • #50

Closed
Open
Opened Mar 02, 2020 by Jens Petit@jens.petitContributor

Not initialize empty DataContainer with 0 per default

When an empty DataContainer is constructed, there should be the option to do it without initializing all values to zero, as this can be an expensive operation for a large container. In many cases, the values are being overwritten anyway right after creating it.

The option to not initialize the values exists for the DataHandlerCPU but is not yet made available at the container level.

To discuss: should the default be to initialize (aka set zero) the values or not? I would advocate for setting the default to not initialize the values for performance reasons.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: IP/elsa#50