From: Samuel Abels <newsgroups@debain.org>
To: david@lang.hm
Cc: git@vger.kernel.org
Subject: Re: Performance impact of a large number of commits
Date: Fri, 24 Oct 2008 21:56:42 +0200 [thread overview]
Message-ID: <1224878202.7566.25.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.1.10.0810241240100.27333@asgard.lang.hm>
On Fri, 2008-10-24 at 12:43 -0700, david@lang.hm wrote:
> 100,000 commits per day??
>
> that's 1.5 commits/second. what is updating files that quickly?
This is an automated process taking snapshots of rapidly changing files
containing statistical data. Unfortunately, our needs go beyond what a
versioning file system has to offer, and the data is an unstructured
text file (in other words, using a relational database is not a good
option).
> I suspect that you will have some issues here, but it's going to depend on
> how many files get updated each 3/4 of a second.
That would be 5 to 10 changed files per commit, and those are passed to
git commit explicitly (i.e., walking the tree to stat files for finding
changes is not necessary).
-Samuel
next prev parent reply other threads:[~2008-10-24 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 19:02 Performance impact of a large number of commits Samuel Abels
2008-10-24 19:43 ` david
2008-10-24 19:56 ` Samuel Abels [this message]
2008-10-24 20:11 ` david
2008-10-25 5:18 ` Samuel Abels
2008-10-25 5:29 ` david
2008-10-25 15:12 ` Samuel Abels
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=1224878202.7566.25.camel@localhost \
--to=newsgroups@debain.org \
--cc=david@lang.hm \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.