Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #541
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

show log is extremely slow

By mwisni... on September 08, 2010 00:51 (imported from Google Code)


What steps will reproduce the problem?

  1. clone git://git.kernel.org/pub/scm/git/git.git
  2. use "Show log" menu
  3. wait ridiculous amount of time locally (10min?) or forever (hours?) when working on network drive.

What is the expected output? What do you see instead?
gitk shows same output in 10s locally or 20s from network drive.

What version of the product are you using? On what operating system?
TortoiseGit 1.5.3.0
git version 1.7.0.2.msysgit.0

Please provide any additional information below.
TortoiseProc.exe maxes out single CPU but does rather slow IO. Using procmon.exe I have observed that it constantly (1000s of times per second) re-reads .gitattributes files.

Stack summary (Location, CPU-time):
TortoiseProc.exe 100%

  • ntdll.dll+0x33021 100%
    • kernel32.dll+0x1f56d 100%
      • Hunspell::get_csconv+0x180ae 0%
      • MSVCR90.dll+0x2fdf 99%
        • mfc90u.dll+0x6db3d 99%
          • Hunspell::get_csconv+0x8ead3 99%
            • Hunspell::get_csconv+0x8e894 99%
              • TortoiseProc.exe+0x8dc5b 99%
                • git_diff+0x35 2%
                • git_diff+0x4e 21%
                  • git_check_excluded_1 21%
                • git_diff+0x90 76%
                  • git_check_excluded_1 76%

a lot of calls to git_check_excluded_1 follows below.

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