TortoiseGit - 慢显示日志修订查询
目前，我们遇到 TorotiseGit - Show Log 需要很长时间才能填充分支/标签历史记录的问题。另一方面，GIT GUI 可以立即显示修订版本。尽管 GIT GUI 需要双击修订版本才能查看更改的内容。
我们有一个包含 300,000 个文件的存储库，最近进行了大约 3000 个修订，管理员对主目录之一进行了 SVN 移动。是的，这意味着所有 250,000 个文件都从一个目录移动到下一个目录。这可能是速度变慢的原因。
有没有一种方法可以加快 TorotiseGit 的速度，以便在处理大型 svn 存储库的情况下更快地显示日志结果。
Currently we have a problem with TorotiseGit - Show Log taking ages to populate branch/tags history. On the other hand GIT GUI shows the revision all-most instantly. Though GIT GUI requires double clicking on the revision to see what's changed.
We have a repository with 300,000 files and recently about 3000 revisions ago, the administrator did a SVN move of one of the main directory's. Yes this means all 250,000 files where moved from one directory to the next. This may be the reason for the slow down.
Is there a way to speed up TorotiseGit to show log results faster in situations dealing with large svn repositories.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
答案是 git 没有每个文件的历史记录，因此它会遍历整个存储库来构建单个文件历史记录。对于巨大的存储库，这成为一个问题。
the answer is git doesn't have per file history, so it traverse the whole repository to build a single file history. with huge repository this becomes a problem.
我克隆了包含 40-50 GB 内容的 SVN 存储库。乌龟Git
花了 15 分钟才调出单个文件的修订日志。尽管使用内置的 GIT GUI 访问相同的修订日志要快得多。
距离这个关于堆栈溢出的原始答案已经过去了大约 3-4 年。尽管 TortoiseGit 的性能多年来可能已经发生了变化，并且可能与内置的 GIT GUI 一样快。如果处理大型 40-50 gig svn repro，我的建议是克隆 svn 存储库并将其托管在本地，或使用内置的 GIT GUI。
I cloned our SVN repository that contains 40-50 gigs of content. TortoiseGit
took 15 minutes to bring up a revision log of a single file. Though accessing the same revision log with the inbuilt GIT GUI was significantly faster.
It's been about 3-4 years since this original answer on stack overflow. Though the performance of TortoiseGit may have changed over the years and could be just as fast as the inbuilt GIT GUI. My recommendations if dealing with large 40-50 gig svn repro is to clone the svn repository and host it locally, or use the inbuilt GIT GUI.
我们也遇到了这个问题 - （几乎）在根级别通过 git GUI 即时查看日志，但通过 TGit 查看单个文件需要 10 分钟。
然后（由于不相关的原因）我们的防病毒软件（不确定是哪个 - 计算机被锁定）被禁用，并且......几乎可以即时查看各个文件的 TGit 日志！
所以我猜想，对于检索到的每个日志片段，反病毒软件必须启动并逐段检查它。
顺便说一句，我们的 Repo 大约为 12GB，并分为 1GB 块
We had this problem too - (almost) instant log view at root level and via git GUI, but 10's of minutes for an individual file via TGit.
Then (for unrelated reasons) our AntiVirus (not sure which - computers locked down) was disabled, and ... almost instant TGit log view of individual files!
So I guess that, for each fragment of log that was retrieved, the AV had to fire up and examine it piece by piece.
BTW our Repo is about 12GB and split into 1GB chunks