Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dorie
  • dorie
  • Issues
  • #76

Closed
Open
Opened Jul 25, 2018 by Lukas Riedel@lriedelOwner

Make compilation procedure more efficient

Description

The current compilation procedure is focused on not exceeding 2 GB of RAM for sequential make runs. As indicated in !63 (merged), compiling single instantiations of the Simulation template can be inefficient, both in terms of memory and CPU usage.

The new restrictive limit is the default GitLab runner, which is limited to 3 GB.

Proposal

Use less object files:

  1. Move multiple YASPGrid instantiations into one object file
  2. (optional) Move more UGGrid instantiations into single object files

How to test the implementation?

Pipeline passes (faster than now)

Related issues

See !63 (merged).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dorie/dorie#76