From: Nicolas Pitre <nico@cam.org>
To: Keith Packard <keithp@keithp.com>
Cc: git@vger.kernel.org
Subject: observations on parsecvs testing
Date: Thu, 15 Jun 2006 16:37:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606151529350.16002@localhost.localdomain> (raw)
My machine is a P4 @ 3GHz with 1GB ram.
Feeding parsecvs with the Mozilla repository, it first ran for 175
minutes with about 98% CPU spent in user space reading the 100458 ,v
files and writing 700000+ blob objects. Memory usage grew to 1789MB
total while the resident memory saturated around 700MB. This part was
fine even with 1GB of ram since unused memory was gently pushed to swap.
Only problem is that spawned git-pack-object instances started failing
with memory allocation by that time, which is unffortunate but not
fatal.
But then things started to go bad after all ,v files were parsed. The
parsecvs dropped to 3% CPU while the rest of the time was spent waiting
after swap IO and therefore no substantial progress was made at that
point.
So the Mozilla clearly requires 2GB of ram to realistically be converted
to GIT using parsecvs, unless its second phase is reworked to avoid
totally random access in memory in order to improve swap behavior, or
its in-memory data set is shrinked at least by half.
Also rcs2git() is very inefficient especially with files having many
revisions as it reconstructs the delta chain on every call. For example
mozilla/configure,v has at least 1690 revisions, and actually converting
it into GIT blobs goes at a rate of 2.4 objects per second _only_ on my
machine. Can't objects be created as the delta list is walked/applied
instead? That would significantly reduce the initial convertion time.
Nicolas
next reply other threads:[~2006-06-15 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 20:37 Nicolas Pitre [this message]
2006-06-15 22:03 ` observations on parsecvs testing Keith Packard
[not found] ` <20060615164742.570e33a0.seanlkml@sympatico.ca>
2006-06-15 20:47 ` Sean
2006-06-15 20:55 ` Nicolas Pitre
2006-06-15 22:04 ` Keith Packard
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=Pine.LNX.4.64.0606151529350.16002@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=keithp@keithp.com \
/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).