Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • maestro-core maestro-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • maestro
  • maestro-coremaestro-core
  • Issues
  • #93

Improve performance of mstro_attribute_val_cmp_str

ECMWF's workflow shows excessive cost of mstro_attribute_val_cmp_str.

Avoid allocation for small attribute value types is the first attempt. We also need to check which comparisons trigger this exactly -- if would be great to have a self-contained reproducer that can be profiled outside of the ECMWF workflow.

  • avoid alloc/free for small types
  • check whether we could cache the value for repeated conversions on the same CDO/ same subscription
  • build reproducer for profiling?
Edited Nov 16, 2021 by Utz-Uwe Haus
Assignee
Assign to
Time tracking