Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5,347
    • Issues 5,347
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 568
    • Merge requests 568
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • 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
  • Glasgow Haskell CompilerGlasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #20891
Closed
Open
Issue created Dec 30, 2021 by Matthew Pickering@mpickeringDeveloper

MHU: Downsweep can be quite slow with a lot of modules and packages (1800 modules/139 packages)

It seems there is some opportunity to improve the speed and progress reporting of downsweep.

  1. When you have a lot of packages an option to indicate progress would be nice (related to #20877)
  2. Seems that there is some opportunity for parallelism, can assign n packages per thread and have thread-local storage to store the downsweep cache. (To avoid global lock on the cache).
  3. Some normal profiling to make sure there's no obvious hotspots (ie looking things up in long lists).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking