Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • O Open ZGY
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Upcoming Change to GitLab Pages The GitLab Pages URL is planned to migrate from the current *.pages.community.opengroup.org to a simpler domain: *.pages.opengroup.org. At the same time, HTTPS will be enabled for the server. This change is planned for May 21, 2022.

If you have questions or concerns, please email forum-support@opengroup.org.

  • Open Subsurface Data Universe Software
  • Platform
  • Domain Data Mgmt Services
  • Seismic
  • Open ZGY
  • Merge requests
  • !80

Merged
Created Jul 05, 2021 by Paal Kvamme@kvamme3Maintainer

Malloc tweak

  • Overview 1
  • Commits 3
  • Pipelines 2
  • Changes 6

Improve OpenZGY read performance when the application requests just a single brick or part of a brick at a time, from multiple threads, and is run in a high-performance (>= 48 core machine) on Azure (i.e. not Google) with co-located data storage, and the application isn't doing other work than reading data. For Petrel this is mainly when using "Prefetch to cache" but there may be other workflows where the tweak is noticeable.

The tweak is automatically skipped if reading larger areas that make the consolidate-bricks logic kick in. Apart from that the tweak will be active. But except for the case described above it probably won't have any measurable effect. Because there will be other factors that slow down the throughput a lot more.

More description will be added as comments. The text in the description box is only allowed 4000 characters.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: kvamme62/malloc-tweak