Project

General

Profile

Forums » Help »

Repository.fetch_changesets takes forever (over an hour with 100% CPU)

Added by Ted S about 14 years ago

I just upgraded to version .9 from .8. We have a LARGE git repository and we have been keeping the repo in sync with Redmine using the following simple post-receive hook:

cd /usr/local/redmine/<cloned repo>
git fetch
cd /WWW/redmine
ruby script/runner "Repository.fetch_changesets" -e production

This has worked well and it runs in a matter of seconds per commit, however, when moving to .9, it now takes on average of 65 minutes, eating 100% of CPU on one (of two) processors. I have gone through the forums and I cannot find anything specific to this issue.

I am running version 3403 of Redmine
Redhat AS 5.x
git 1.5.4.3
Rails 2.3.5
Ruby 1.8.6

Any help would be greatly appreciated.


Replies (2)

RE: Repository.fetch_changesets takes forever (over an hour with 100% CPU) - Added by Ted S about 14 years ago

Additional information:

We have 6381 revisions in our git repo, taking ~250MB.

./reporefresh.sh
+ cd /usr/local/redmine/repo
+ git fetch
remote: Counting objects: 18, done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 13 (delta 7), reused 0 (delta 0)
Unpacking objects: 100% (13/13), done.
From :repo
ae3a1ac..845cfb6 master -> master
+ cd /WWW/redmine
+ ruby script/runner Repository.fetch_changesets -e production

real 63m45.634s
user 55m24.402s
sys 5m48.634s

Any help would be greatly appreciated.

RE: Repository.fetch_changesets takes forever (over an hour with 100% CPU) - Added by Ted S about 14 years ago

I think 3394 solved the issue, I did not realize that 3393 was the end of the current .9 branch of the repo.

    (1-2/2)