From: "Dana How" <danahow@gmail.com>
To: "Martin Koegler" <mkoegler@auto.tuwien.ac.at>
Cc: "Junio C Hamano" <junkio@cox.net>,
git@vger.kernel.org, danahow@gmail.com
Subject: Re: [PATCH] git-pack-objects: cache small deltas between big objects
Date: Sun, 20 May 2007 21:35:56 -0700 [thread overview]
Message-ID: <56b7f5510705202135s8c9cd9qf4489b2b5bb2e264@mail.gmail.com> (raw)
In-Reply-To: <11796954641778-git-send-email-mkoegler@auto.tuwien.ac.at>
On 5/20/07, Martin Koegler <mkoegler@auto.tuwien.ac.at> wrote:
> Creating deltas between big blobs is a CPU and memory intensive task.
> In the writing phase, all (not reused) deltas are redone.
Actually, just the ones selected, which is approx 1/window.
Do you have any numbers describing the effects on runtime
and memory size for a known repo like linux-2.6?
> This patch adds support for caching deltas from the deltifing phase, so
> that that the writing phase is faster.
>
> The caching is limited to small deltas to avoid increasing memory usage very much.
> The implemented limit is (memory needed to create the delta)/1024.
Your limit is applied per-object, and there is no overall limit
on the amount of memory not freed in the delta phase.
I suspect this caching would be disastrous for the large repo
with "megablobs" I'm trying to wrestle with at the moment.
> @@ -1294,10 +1302,17 @@ static int try_delta(struct unpacked *trg, struct unpacked *src,
> trg_entry->delta = src_entry;
> trg_entry->delta_size = delta_size;
> trg_entry->depth = src_entry->depth + 1;
> - free(delta_buf);
> + /* cache delta, if objects are large enough compared to delta size */
> + if ((src_size >> 20) + (trg_size >> 21) > (delta_size >> 10))
> + trg_entry->delta_data = delta_buf;
> + else
> + free(delta_buf);
> return 1;
> }
--
Dana L. How danahow@gmail.com +1 650 804 5991 cell
next prev parent reply other threads:[~2007-05-21 4:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 21:11 [PATCH] git-pack-objects: cache small deltas between big objects Martin Koegler
2007-05-21 4:35 ` Dana How [this message]
2007-05-21 17:59 ` Martin Koegler
2007-05-22 7:01 ` Dana How
2007-05-22 8:04 ` Junio C Hamano
2007-05-22 9:25 ` Dana How
2007-05-21 4:54 ` Junio C Hamano
2007-05-21 17:00 ` Martin Koegler
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=56b7f5510705202135s8c9cd9qf4489b2b5bb2e264@mail.gmail.com \
--to=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mkoegler@auto.tuwien.ac.at \
/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).