From: "Yakov Lerner" <iler.ml@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: 'push origin master' takes over 8 minutes (local ssh)
Date: Sat, 14 Jul 2007 16:00:44 +0300 [thread overview]
Message-ID: <f36b08ee0707140600i5dc25056k4c95a432ec225a83@mail.gmail.com> (raw)
Something happened to the repo, and 'push origin master'
is taking now very long time: > 8 minutes (this is ssh to localhost).
It's in git-pack-objects.
The git-pack-objects sits there for >8 minutes using very low cpu (<1 %)
but lots of RAM (>300MB). Then it bombs with malloc error.
I could add swap to the machine [1], but this long time with
low cpu usage is suspicious, no ?
Repo counters are below [2]
I suspect one file, history of which accumulated thousands commits
from the script. I'd like to erase the history of this file but I don't know
how. And I don't know where there is a connection.
Yakov
[1] This is vps machine that hasb 128MB ram + 256MB swap.
[2] Repo counters.
- the master repo which is being pushed to (it is bare, the "master" repo):
count: 653
size: 140692
in-pack: 21730
packs: 2
prune-packable: 5
garbage: 0
the repo which does the push:
count: 369
size: 42960
in-pack: 22145
packs: 4
prune-packable: 9
garbage: 0
Don't ask me about workflow.
I synchronize files between four hosts using git.
I beleive this is very unusual workflow. No branches.
reply other threads:[~2007-07-14 13:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f36b08ee0707140600i5dc25056k4c95a432ec225a83@mail.gmail.com \
--to=iler.ml@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).