Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 836
    • Issues 836
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #5269

Closed
Open
Created Oct 22, 2018 by Bitbucket Importer@bitbucket_importerOwner

large repositories in tortoise are torturously slow since 4.7.2 update

Created originally on Bitbucket by Anonymous

Update operations in moderately large repositories are very slow now and tortoise is sustained cpu usage for the duration.

This is even true if say i update from the command line, the command line returns very quickly but tortoise then sits at 100% of one core CPU

we're talking ~5 seconds to update from one point to another in the ui and < 0.5 in command line. commit ets also taking as long in the ui

reverting to 4.7.1 makes it fast again (but repeated branch names are broken) there's bugs for like the past 5 versions so I'm going back to 4.5.0

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking