Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E elsa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IP
  • elsa
  • Issues
  • #50

Closed
Open
Created 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
Time tracking